Skip to content

[DOCS] Backport of troubleshooting high cpu. Opster migration #125558

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

Open
wants to merge 3 commits into
base: 8.17
Choose a base branch
from

Conversation

thekofimensah
Copy link
Contributor

@thekofimensah thekofimensah commented Mar 25, 2025

This is importing additional information given in the Opster docs for high cpu issues.

Summary of changes:

  1. Moved the “Hotspotting” paragraph at the beginning into the “Tips and Solutions” section for better contextual fit, incorporating extra details from the Opster documentation.
  2. Added new subsections to “Tips and Solutions,” specifically covering JVM garbage collection and oversharding.
  3. Separated the previous three points (“Scale your cluster,” “Spread out bulk requests,” and “Cancel long-running searches”) into a distinct section, as they are less common scenarios and more general best practices rather than direct solutions to typical high CPU issues.

V9 here: elastic/docs-content#909

Copy link
Contributor

Documentation preview:

@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v8.17.5 external-contributor Pull request authored by a developer outside the Elasticsearch team labels Mar 25, 2025
@AI-IshanBhatt AI-IshanBhatt added the >docs General docs changes label Mar 26, 2025
@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team and removed needs:triage Requires assignment of a team area label labels Mar 26, 2025
@elasticsearchmachine
Copy link
Collaborator

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

@thekofimensah
Copy link
Contributor Author

@georgewallace

@shainaraskas shainaraskas added auto-backport Automatically create backport pull requests when merged v8.18.1 labels Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged >docs General docs changes external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Docs Meta label for docs team v8.17.7 v8.18.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants