How do I troubleshoot high JVM memory pressure on my Elasticsearch cluster?
Last updated: 2019-07-17
My Amazon Elasticsearch Service (Amazon ES) cluster has high JVM memory pressure. How can I resolve this?
If JVM memory pressure is consistently above 75%, then your Elasticsearch cluster probably doesn't have enough resources to support the amount of data or the query load. Temporary spikes in the JVMMemoryPressure metric aren't necessarily a problem. However, if JVM memory pressure stays high for more than a few minutes, your cluster might experience a ClusterBlockException, JVM OutOfMemoryError, or other performance problems. To troubleshoot high JVM memory pressure, see Why did my Elasticsearch node crash?