FAQ - What is the consequence of increasing high-water-memory-pct?

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

FAQ - What is the consequence of increasing high-water-memory-pct ?


There are a number of tunables within Aerospike to manage node resource usage. One of these is high-water-memory-pct which defines the threshold of memory at which eviction will start. What is the consequence of raising this past default levels?


If appropriate to the use case, there is no issue with increasing high-water-memory-pct, however the effects should be understood. When setting high-water-memory-pct, the key thing to bear in mind is that this is not a hard limit on memory usage, it is the point at which evictions due to memory usage start. It is quite possible for the high-water-memory-pct to be breached, for evictions to start and for memory usage to continue to climb past 100% of what has been allotted for the namespace. As evictions can be relatively slow (dependent on various tuning factors) it is not inconceivable that the system could run out of memory while evictions are happening.

With this in mind, high-water-memory-pct should be set with sufficient headroom to ensure that the system does not run out of memory in the event of it being breached.


The following article discusses various Aerospike defaults and the reasons for their value:

The article linked below deals with high-water-disk-pctand how this is related to defragmentation: