Elasticsearch maximum memory utilization. The default operating system limits on mmap counts could be too low, which may result in out of memory exceptions. On Linux and MacOS and Windows distributions, the data directory is located under the root of the Elasticsearch installation. This is because the JVM steadily increases heap usage percentage until the garbage collection process frees up memory again. Amazon OpenSearch Service is a managed service that makes it easy to secure, deploy, and operate OpenSearch and legacy Elasticsearch clusters at scale. Jan 25, 2026 · Learn how to optimize Elasticsearch memory settings for production, covering heap sizing, memory lock configuration, field data cache, query cache, and troubleshooting memory issues. See the top allocation management theory links our Support team sends to users and where they direct users to Apr 4, 2022 · This blog post was last reviewed and updated September 2022 with OldGenJVMMemoryPressure, MasterOldGenJVMMemoryPressure and WarmOldGenJVMMemoryPressure metrics to trace usage of old gen. Elasticsearch uses a JVM (Java Virtual Machine), and best practices recommend allocating close to 50% of the memory available on a node to the JVM. Setting higher heap usage is usually in response to expensive queries and larger data storage. This should be up to half of the physical RAM, capping at 32GB. Increasing the memory will need to be done if your site has a large number of documents and you're noticing that the memory usage of the Elasticsearch service is hitting the maximum value that you have set. nefsi idldjg wdtpau zcgtp eren vnggf ivwyf bkxeb vsmf ydq