Aerospike Shared-Memory Tool (ASMT) supports faster cold starts of nodes in an Aerospike Database Enterprise Edition (EE) cluster.
ASMT supports saving and restoring the primary index, as well as secondary indexes that are stored in shared memory, a feature introduced in Aerospike EE version 6.1.
This tool is not intended for namespaces where the primary index is configured on Persistent Memory or Flash (SSDs), as those would persist upon an instance restart.
If you needed to restart the server hosting an Aerospike Database cluster node, you would:
- Cleanly shut down the Aerospike cluster node process (
asmtto save the node's primary index by copying it from shared memory to files on your file system.
- Reboot the server.
- After the server restarts, use
asmtto restore the primary index from its copy on file system to shared memory.
- Perform a cold start of your Aerospike node.
This restart will now be faster because the cluster finds the index in shared memory and does not have to reconstruct it. The alternative, reconstructing the primary index from the drives, is a much longer process, and requires the Aerospike cluster node to scan all the storage devices.
You cannot use ASMT while the Aerospike Database process is running.
Refer to the following knowledge base articles: