Expand High CPU Troubleshooting #4499
Conversation
Vale Linting ResultsSummary: 1 warning, 2 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| troubleshoot/elasticsearch/high-cpu-usage.md | 176 | Elastic.BritishSpellings | Use American English spelling 'behavior' instead of British English 'behaviour'. |
💡 Suggestions (2)
| File | Line | Rule | Message |
|---|---|---|---|
| troubleshoot/elasticsearch/high-cpu-usage.md | 17 | Elastic.Wordiness | Consider using 'all' instead of 'all of '. |
| troubleshoot/elasticsearch/task-queue-backlog.md | 153 | 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.
|
👋🏽 @elastic/admin-docs, I will try to start marking my PRs WIP until they pass linter to avoid noise sorry, but this should be ready for y'alls review now (and if linter fails again, will you kindly advise) 🙏 |
|
Hey @stefnestor, Thanks for opening this! Would it be alright with you if I pull the PR down locally and push a few changes? (I went ahead and added a commit to fix up the docs build. :-) ) |
| Users with an [Elastic subscription](https://www.elastic.co/pricing) can [request Elastic's assistance]](/troubleshoot.md#contact-us) reviewing this output. When doing so, kindly ensure: | ||
|
|
||
| * Grant written permission for Elastic to review your uploaded heap dumps within the support case. | ||
| * Share only after receiving any necessary business approvals as this file might contain private information. Files are handled according to [Elastic's privacy statement](https://www.elastic.co/legal/privacy-statement). |
There was a problem hiding this comment.
| * Share only after receiving any necessary business approvals as this file might contain private information. Files are handled according to [Elastic's privacy statement](https://www.elastic.co/legal/privacy-statement). | |
| * Share this file only after receiving any necessary business approvals as it might contain private information. Files are handled according to [Elastic's privacy statement](https://www.elastic.co/legal/privacy-statement). |
| * [Inspect hot threads on each node](#diagnose-task-queue-hot-thread) | ||
| * [Identify long-running node tasks](#diagnose-task-queue-long-running-node-tasks) | ||
| * [Look for long-running cluster tasks](#diagnose-task-queue-long-running-cluster-tasks) | ||
| * [Monitor Slow Logs](#diagnose-task-slow-logs) |
There was a problem hiding this comment.
| * [Monitor Slow Logs](#diagnose-task-slow-logs) | |
| * [Monitor slow logs](#diagnose-task-slow-logs) |
|
|
||
| Tasks with a high `timeInQueue` value are likely contributing to the backlog and might need to be [canceled](#resolve-task-queue-backlog-stuck-tasks). | ||
|
|
||
| ### Monitor Slow Logs [diagnose-task-slow-logs] |
There was a problem hiding this comment.
| ### Monitor Slow Logs [diagnose-task-slow-logs] | |
| ### Monitor slow logs [diagnose-task-slow-logs] |
|
|
||
| ### Monitor Slow Logs [diagnose-task-slow-logs] | ||
|
|
||
| If you're not present during incident to investigate backlogged tasks, you might consider enabling [Slow Logs](elasticsearch://reference/elasticsearch/index-settings/slow-log.md) to review later. |
There was a problem hiding this comment.
| If you're not present during incident to investigate backlogged tasks, you might consider enabling [Slow Logs](elasticsearch://reference/elasticsearch/index-settings/slow-log.md) to review later. | |
| If you're not present during an incident to investigate backlogged tasks, you might consider enabling [slow logs](elasticsearch://reference/elasticsearch/index-settings/slow-log.md) to review later. |
There was a problem hiding this comment.
LGTM! 🦘
@stefnestor this is superb! Very, very nice work. The organization here is so much better than what we had before. I added lots of comments but they're all just minor phrasing things.
"allocated_processors in CAT nodes isn't available till v9.3.0 per elastic/elasticsearch#134692, (how) do we mark that?"
This suggestion (below) will add an "applies_to" tag to mark 9.3 GA.
Co-authored-by: David Kilfoyle <[email protected]>
kilfoyle
left a comment
kilfoyle
left a comment
There was a problem hiding this comment.
LGTM! 🦖
Thanks Stef!!! What a nice improvement for our docs.
|
Cheers, @kilfoyle! Thanks for your help on this! The very top part of CPU-vs-Java-vs-threads needs an ES Dev sign-off. I will request in Slack but please LMK if your team has a Github way of directing this to them 🙏 |
Sounds good! There are several |
|
@stefnestor I've tagged the ES performance team for review. |
|
Bump for @elastic/es-perf review 🙏 |
2 participants
Summary
👋 Ports High CPU article to docs.
🙋♀️
allocated_processorsin CAT nodes isn't available till v9.3.0 per this, (how) do we mark that?Related understanding for top summary portion changes from
🙏 TIA!
Generative AI disclosure