Skip to main content

Speeding Up Cold Starts with the Aerospike Shared-Memory Tool (asmt)

Aerospike Shared-Memory Tool (asmt) lets you perform faster cold starts of nodes in an Aerospike Database Enterprise Edition cluster.

Here is an example outline of the steps for using it. In this situation, the server that hosts an Aerospike node needs to be rebooted.

  1. Shut down a node in an Aerospike cluster cleanly.
  2. Use asmt to save the node's primary index by copying the index from shared memory to files in the file system.
  3. Reboot the server that is hosting the node.
  4. After the server restarts, use asmt to restore the index by copying it from the file system to shared memory.
  5. Perform a cold start of your Aerospike node.

The cold start is faster because the cluster finds the index in shared memory and does not have to reconstruct it. The alternative -- reconstructing the primary index without reading it from shared memory, a much longer process -- requires the Aerospike cluster to scan all of the records in the database.


You cannot use asmt while your Aerospike cluster is running.

You can download a compiled binary of asmt, which is statically built on CentOS 7 and should work for most x86-64 Linux distributions.

Alternatively, you can compile asmt yourself.


This tool is of course not intended for namespaces with their primary index configured on PMEM or Flash as those would persist upon an instance restart.

Also refer to the following knowledge base articles: