-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Shutdown API for shutting down nodes in a safe manner #1304
Comments
Hello @rramachand21! Can you please fill this out with more information about the enhancement you want to make? We need more information to understand the problem and the enhancement. Thank you! |
Hello @rramachand21 Could you add more details to this issue? If you aren't able to provide more details by 10/22, I will close the issue - but feel free to reopen it later when you've got more information. Thanks, |
@rramachand21 I've resolved this issue, but please feel free to re-open it and provide more information. Thanks, |
@CEHENKLE how can I reopen this issue? Would love to add more details to this. Do I need to open a new issue? |
I've reopened it, thanks. |
@rramachand21 Any further thoughts on this? Thanks! /C |
@CEHENKLE updated the overview section |
add related content in ES
this feature useful for me too. I would like using preStop hooks in Kubernetes to graceful stopping OS nodes. Like this script https://github.com/elastic/cloud-on-k8s/blob/main/pkg/controller/elasticsearch/nodespec/lifecycle_hook.go#L29 |
Any updates on this? Since OpenSearch 2.12, I'm unable to cleanly shut down the service in a Dockerfile |
@ben-gineer AFAIK nobody is working on this, please contribute! |
Added PR for this issue. |
Is your feature request related to a problem? Please describe.
When a user wants to remove node out of the cluster, there is no easy way to move the ongoing tasks and index shards to other nodes. Also shards should not be migrated to the node being removed out of the cluster.
Describe the solution you'd like
Provide an API to safely shutdown nodes
The text was updated successfully, but these errors were encountered: