Memory lock disabled
Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
Memory locking is turned off (bootstrap.memory_lock: false), so the JVM heap is not locked in RAM. If the host swaps heap pages to disk, latency and garbage collection can degrade sharply.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Node |
| Domains | performance, memory, stability |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
bootstrap.memory_lock is false in the cluster settings. The JVM heap is not locked in RAM.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Enable memory lock on nodes
Condition: Always shown for this insight.
As a last resort if OS-level memory locking is not enough, set bootstrap.memory_lock: true in elasticsearch.yml on each affected node, then perform a rolling restart. This keeps the JVM heap from being swapped out.
Enable OS memory lock
Condition: Always shown for this insight.
Turn off memory swap so Elasticsearch can lock heap in RAM. On Linux, comment out swap entries in /and so on/fstab, or set vm.swappiness to 1. On Windows, turn off the paging file under System Properties → Advanced → Performance → Advanced → Virtual memory.
Elasticsearch performance depends on keeping the JVM heap in physical memory. If the operating system swaps heap pages to disk, search and indexing latency spike and garbage collection can stall the node.
Setting bootstrap.memory_lock to true asks Elasticsearch to lock the JVM heap in RAM. The host must also allow the lock (for example, memlock limits). The memory-lock bootstrap check fails when bootstrap.memory_lock is true and the JVM could not lock the heap, not because swap is still enabled. Disabling swap at the operating system level is an alternative to memory locking.
Until memory lock is enabled or swap is turned off, the node remains exposed to swap-related latency and instability under memory pressure.