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

[Docs] Add a warning to the default max number of shards allowed in a cluster #35943

Closed
tlrx opened this issue Nov 27, 2018 · 3 comments
Closed
Assignees
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >docs General docs changes v6.6.0 v7.0.0-beta1

Comments

@tlrx
Copy link
Member

tlrx commented Nov 27, 2018

The cluster.shards.max_per_node setting has been added in #34021 & #34892 as a soft limit on the number of shards that are allowed in a cluster, with the default ratio of 1,000 shards per node.

I do not question this default value but I think that we should make it really clear in the doc (under a WARNING section or something) that this default value could already be too high for many clusters. The risk I see here is people interpreting that "it is OK to have 1,000 shards on 1 Elasticsearch node" because this is the max default value we propose.

@tlrx tlrx added >docs General docs changes :Data Management/Indices APIs APIs to create and manage indices and templates v7.0.0 labels Nov 27, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@tlrx
Copy link
Member Author

tlrx commented Nov 27, 2018

@gwbrown I'm raising this to your attention :)

@gwbrown
Copy link
Contributor

gwbrown commented Nov 27, 2018

This is a great point, thanks for bringing it up. I'll add this note shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >docs General docs changes v6.6.0 v7.0.0-beta1
Projects
None yet
Development

No branches or pull requests

4 participants