-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Add note on the danger of closed indices #61332
Add note on the danger of closed indices #61332
Conversation
Prior to elastic#33888 it is dangerous to keep closed indices in your cluster long-term: Elasticsearch does not maintain their shard copies so they tend to get lost as the cluster migrates to new nodes. This risk isn't documented today. This commit addresses that gap.
Pinging @elastic/es-docs (>docs) |
Pinging @elastic/es-core-features (:Core/Features/Indices APIs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall.
I left a few minor comments, but this is largely good as-is.
Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
Thanks James, I accepted your rewrite :) |
https://www.elastic.co/cloud/elasticsearch-service/signup[try out the hosted service] for free. | ||
Elasticsearch can be run on your own hardware or using our hosted Elasticsearch | ||
Service on https://www.elastic.co/cloud[Elastic Cloud], which is available on | ||
AWS, GCP and Azure. You can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated except that I was looking for other references to Cloud: reformat & mention Azure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few minor suggestions. The attributes should probably be added,
but otherwise feel free to take/leave as you see fit.
Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Prior to #33888 it is dangerous to keep closed indices in your cluster
long-term: Elasticsearch does not maintain their shard copies so they
tend to get lost as the cluster migrates to new nodes. This risk isn't
documented today. This commit addresses that gap.