Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ejob-lite why not let servers as ephemeral node? What other considerations are there? #2165

Closed
huaronghao opened this issue Dec 12, 2022 · 1 comment
Labels

Comments

@huaronghao
Copy link

When we use k8s deploy our service which integrated with ejob-lite,service IP is always not fixed. Zookeeper Servers node list is getting longer and longer. JobShutdownHookPlugin won't clear services node, and servers node also not as ephemeral node, both have other considerations?

@songxiaosheng
Copy link
Member

songxiaosheng commented Mar 14, 2023

When we use k8s deploy our service which integrated with ejob-lite,service IP is always not fixed. Zookeeper Servers node list is getting longer and longer. JobShutdownHookPlugin won't clear services node, and servers node also not as ephemeral node, both have other considerations?

Persistent nodes are used to record the status whether the current IP status is restarted or not. They can be recorded, such as disabled or specified.

Temporary nodes are used to record the process survival status. The temporary nodes have process IDs on them. If it is not necessary to record these status nodes, it is also a solution to consider moving the persistent nodes out of the container environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants