It could be due to some fragmentation as you are using a storage-engine memory configuration. The heap memory line in the logs may give you some hints. My response on this topic: Aerospike in-memory DB uses much memory than expected - #23 by helper_bro may help. The memory allocated for the primary index would indeed not be freed up without a restart but the memory allocated for the data (since you are data in memory) should be freed up but you could get some fragmentation…
1 Like