Expand hotspotting documentation page #4592
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 - Under Hardware: "Resources experience different network or disk throughputs. For example, if one node’s I/O is lower than its peers. Refer to Use faster hardware for more information". The link has been updated to correctly point to the `Use faster hardware` section rather than the top of the page". 2 - Added a sentence about user-perceptible symptoms under `## Causes`: From a user’s perspective, hot spotting may manifest as slower search responses, delayed indexing, ingestion backlogs, or timeouts during queries and bulk operations. 3 - At the "index level" section, I added this sentence: > It’s important to monitor and be aware of any changes in your data ingestion flow, as sudden increases or shifts can lead to high CPU usage and ingestion delays. Depending on your cluster architecture, optimizing the number of primary shards can significantly improve ingestion performance. For more details, see [Clusters, nodes, and shards](https://www.elastic.co/docs/deploy-manage/distributed-architecture/clusters-nodes-shards). 4 - I’m not sure if this was intentional, but the items listed under the “Causes” section (`## Causes`) use the same header level—for example, “Hardware” is marked as `## Hardware`. That made the text a bit confusing for me to read. I’d suggest nesting the cause items under the “Causes” section—for example, using `### Hardware`.
Contributor
Vale Linting ResultsSummary: 1 warning, 2 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| troubleshoot/elasticsearch/hotspotting.md | 48 | Elastic.DontUse | Don't use 'and/or'. |
💡 Suggestions (2)
| File | Line | Rule | Message |
|---|---|---|---|
| troubleshoot/elasticsearch/hotspotting.md | 48 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/hotspotting.md | 121 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
The Vale linter checks documentation changes against the Elastic Docs style guide.
To use Vale locally or report issues, refer to Elastic style guide for Vale.
Contributor
🔍 Preview links for changed docs |
kilfoyle
approved these changes
Jan 12, 2026
Contributor
kilfoyle
left a comment
kilfoyle
left a comment
There was a problem hiding this comment.
LGTM! 🏎️
Very nice changes! Thanks a lot @rodrigomadalozzo!
1 task
stefnestor
added a commit
that referenced
this pull request
Jan 19, 2026
## Summary Follow-up to #4592, when I originally wrote [hot spotting](https://www.elastic.co/guide/en/elasticsearch/reference/current/hotspotting.html) (elastic/elasticsearch#95429), we didn't have task queue backlog so some of its kind of content ended up over there. Undoes that and adds in content related to - (@mlliarm) https://support.elastic.co/knowledge/21401798 - (@rodrigomadalozzo) https://support.elastic.co/knowledge/d6496673 ## Generative AI disclosure 1. Did you use a generative AI (GenAI) tool to assist in creating this contribution? - [ ] Yes - [X ] No --------- Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1 - Under Hardware: "Resources experience different network or disk throughputs. For example, if one node’s I/O is lower than its peers. Refer to Use faster hardware for more information". The link has been updated to correctly point to the
Use faster hardwaresection rather than the top of the page.2 - Added a sentence about user-perceptible symptoms under
## Causes: From a user’s perspective, hot spotting may manifest as slower search responses, delayed indexing, ingestion backlogs, or timeouts during queries and bulk operations.3 - At the "index level" section, I added this sentence:
4 - I’m not sure if this was intentional, but the items listed under the “Causes” section (
## Causes) use the same header level—for example, “Hardware” is marked as## Hardware. That made the text a bit confusing for me to read. I’d suggest nesting the cause items under the “Causes” section—for example, using### Hardware.@stefnestor
Generative AI disclosure