elasticsearc

Elastic Stack Elasticsearch
1

Dear Elasticsearch Support Team,

I am reaching out to seek guidance regarding an ongoing issue we are experiencing with our Elasticsearch deployment. Despite several troubleshooting efforts, we are unable to resolve the problem effectively.

Issue Description: We have noticed that our Elasticsearch instance is repeatedly reaching the maximum allocated memory limit, specifically 512MB, despite our actual data only consuming around 200MB. We have tried increasing the JVM heap size settings (Xms and Xmx) to 2GB, but the issue persists without improvement.

Troubleshooting Steps Taken:

  1. We verified and increased the JVM heap size as mentioned above.
  2. We reviewed the system and Elasticsearch logs but did not find any clear indications of memory leaks or errors.
  3. We checked the garbage collection logs and did not observe any abnormal behavior.
  4. Our cluster health checks indicate that the cluster is in good health, with no significant shards or replication issues.

System Configuration:

  • Elasticsearch version: [your version here]
  • Number of nodes: [number of nodes]
  • JVM version: [your JVM version here]

We suspect there might be an underlying issue that is not immediately apparent from the logs or our current configuration. Could you please assist us in diagnosing this problem further? Any recommendations or insights you could provide would be greatly appreciated.

Thank you for your support and looking forward to your expert advice.

Best regards,

2

Please tell us which version of Elasticsearch you are using and share any logs that indicate the problem. What exactly happens when you are facing problems?

It would also help to know more about the use case and what load the cluster is under.