Memory lock disabled

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.

Note

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.

Note

AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.

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.