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 max open shards error to 'Size your shards' #77287

Merged
merged 3 commits into from
Sep 10, 2021

Conversation

stefnestor
Copy link
Contributor

@stefnestor stefnestor commented Sep 4, 2021

Changes:

  • Adds a troubleshooting section and documents the maximum shards open error.
  • Retitles the Fix an oversharded cluster to Reduce a cluster's shard count.

Relates to this Elastic Discuss topic.

Appending common error into our Shard sizing docs along w/extra resources commonly viewed from [this Elastic Discuss](https://discuss.elastic.co/t/how-to-fix-hitting-maximum-shards-open-error/200502/2). Top 4 viewed error last 30d on Elastic Discuss.

Kindly assist
- fixing resource links
- I'm debating including [the cluster setting you can temporarily override](https://www.elastic.co/guide/en/elasticsearch/reference/7.14/modules-cluster.html#cluster-shard-limit), but have left it off so far. Would love your thoughts!
@stefnestor stefnestor added >docs General docs changes Team:Docs Meta label for docs team labels Sep 4, 2021
@stefnestor stefnestor requested a review from jrodewig September 4, 2021 03:18
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

@elasticsearchmachine elasticsearchmachine added external-contributor Pull request authored by a developer outside the Elasticsearch team v8.0.0 labels Sep 4, 2021
@jrodewig jrodewig changed the title [+DOC] ERROR: maximum shards open [DOCS] Add max shards open error to 'Size your shards' Sep 9, 2021
@jrodewig
Copy link
Contributor

jrodewig commented Sep 9, 2021

Thanks for this PR @stefnestor. I agree that we should document this error. However, I'm not sure we want to include the external links here. Those links aren't necessarily maintained, and I don't want to link users to outdated info.

I created a new troubleshooting section and included some information about temporarily increasing cluster.max_shards_per_node.

@henningandersen Do you mind taking a look at these changes at your convenience? Thanks!

@jrodewig jrodewig added :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. v7.14.2 v7.15.1 v7.16.0 labels Sep 9, 2021
@elasticmachine elasticmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Sep 9, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@jrodewig jrodewig self-assigned this Sep 9, 2021
@jrodewig jrodewig changed the title [DOCS] Add max shards open error to 'Size your shards' [DOCS] Add max open shards error to 'Size your shards' Sep 9, 2021
Copy link
Contributor

@henningandersen henningandersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one nit.

----

This increase should only be temporary. As a long-term solution, we recommend
you add non-frozen data notes or <<reduce-cluster-shard-count,reduce your
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if rather than non-frozen we should dictate to add nodes for the tier that is oversharded? While today, it is correct that adding a cold node will avoid the limit also for all your hot data, it is not really a solution to the underlying oversharding problem of having too many hot shards for the number of hot nodes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! I'll revise this to:

we recommend you add nodes to the oversharded data tier or ...

jrodewig added a commit that referenced this pull request Sep 10, 2021
Changes:

* Adds a troubleshooting section and documents the `maximum shards open` error.
* Retitles the `Fix an oversharded cluster` to `Reduce a cluster's shard count`.

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: Stef Nestor <[email protected]>
jrodewig added a commit that referenced this pull request Sep 10, 2021
Changes:

* Adds a troubleshooting section and documents the `maximum shards open` error.
* Retitles the `Fix an oversharded cluster` to `Reduce a cluster's shard count`.

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: Stef Nestor <[email protected]>
jrodewig added a commit that referenced this pull request Sep 10, 2021
Changes:

* Adds a troubleshooting section and documents the `maximum shards open` error.
* Retitles the `Fix an oversharded cluster` to `Reduce a cluster's shard count`.

Co-authored-by: James Rodewig <[email protected]>

Co-authored-by: Stef Nestor <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. >docs General docs changes external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. Team:Docs Meta label for docs team v7.14.2 v7.15.1 v7.16.0 v8.0.0-alpha2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants