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

Add a metric for ES memory pressure #661

Merged
merged 3 commits into from
Sep 19, 2024

Conversation

jmuscireum
Copy link
Contributor

Description

The memory pressure of Elasticsearch is supposed to be a good indicator for the performance of the cluster. It is calculated as the usage in percent of the old gen memory pool, as described in https://www.elastic.co/guide/en/elasticsearch/reference/current/high-jvm-memory-pressure.html

We also make the metric available over a public method. This can be used to slow down or pause time-uncritical tasks.

Additional Notes

  • This PR fixes or works on following ticket(s): SE-14021

Checklist

  • Code change has been tested and works locally
  • Code was formatted via IntelliJ and follows SonarLint & best practices
  • Patch Tasks: Is local execution of Patch Tasks necessary? If so, please also mark the PR with the tag.

The memory pressure of Elasticsearch is supposed to be a good indicator for the performance of the cluster. It is calculated as the usage in percent of the old gen memory pool, as described in https://www.elastic.co/guide/en/elasticsearch/reference/current/high-jvm-memory-pressure.html

We also make the metric available over a public method. This can be used to slow down or pause time-uncritical tasks.

Fixes: SE-14021
@jmuscireum jmuscireum added the 🧬 Enhancement Contains new features label Sep 19, 2024
@jmuscireum jmuscireum merged commit 7755581 into develop Sep 19, 2024
3 checks passed
@jmuscireum jmuscireum deleted the feature/es-memory-pressure-metric branch September 19, 2024 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧬 Enhancement Contains new features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants