-
Notifications
You must be signed in to change notification settings - Fork 25k
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
updated shard limit doc #56496
updated shard limit doc #56496
Conversation
As the documentation was not so clear. I have updated saying this limit includes open indices with unassigned primaries and replicas count towards the limit.
Pinging @elastic/es-docs (>docs) |
Pinging @elastic/es-distributed (:Distributed/Allocation) |
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.
Thanks for adding this! Suggested an edit to condense the info about what does/doesn't count toward the limit.
The limit defaults to 1,000 shards per data node, this includes open indices with unassigned primary or replica shards, and can be dynamically | ||
adjusted using the following property: |
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.
I'd combine the info about what counts toward the limit with the info in the previous paragraph. Maybe:
The cluster shard limit defaults to 1,000 shards per data node. Both primary and replica shards of all open indices count toward the limit, including unassigned shards. For example, an open index with 5 primary shards and 2 replicas counts as 15 shards. Closed indices do not contribute to the shard count. You can dynamically adjust the limit with the following property:
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.
++ to updating the content here, with the notes @debadair added.
To add some context, unassigned shards are counted here because this a limit to prevent nodes from becoming unstable due to oversharding. If unassigned shards were not counted, we would likely see those counts spike as soon as the shards become assigned, which would rapidly increase memory usage on the node, possibly causing instability.
@gadekishore @debadair Is this still relevant? |
* updated shard limit doc As the documentation was not so clear. I have updated saying this limit includes open indices with unassigned primaries and replicas count towards the limit. * [DOCS] Incorporated edits. Co-authored-by: Deb Adair <[email protected]>
* updated shard limit doc As the documentation was not so clear. I have updated saying this limit includes open indices with unassigned primaries and replicas count towards the limit. * [DOCS] Incorporated edits. Co-authored-by: Deb Adair <[email protected]>
* updated shard limit doc As the documentation was not so clear. I have updated saying this limit includes open indices with unassigned primaries and replicas count towards the limit. * [DOCS] Incorporated edits. Co-authored-by: Deb Adair <[email protected]> Co-authored-by: gadekishore <[email protected]>
* updated shard limit doc As the documentation was not so clear. I have updated saying this limit includes open indices with unassigned primaries and replicas count towards the limit. * [DOCS] Incorporated edits. Co-authored-by: Deb Adair <[email protected]> Co-authored-by: gadekishore <[email protected]>
As the documentation was not so clear. I have updated saying total shard limit per node includes open indices with unassigned primaries and replicas count towards the limit.