I’m setting up an Aerospike cluster on AWS on an r3 machine (which has local SSD). I’m using the local SSD as namespace device storage, and have an EBS volume of the same size as shadow device. The cluster can be created multiple times and on-demand by other developers with the use of terraform. I currently have ansible scripts to install and configure (networking, namespaces) aerospike on the machines. Basically to spawn a new cluster one runs terraform and then runs ansible, and that should do it.
Normally, the EBS volumes should be zero-ed (
dd if=/dev/zero ...) before being used by aerospike. Is this also the case for shadow devices? And if so: how can I let a script recognize that the volume contains aerospike data or just random stuff? If I’m running the
dd if=/dev/zero ... as part of the user data, it’s executed for every ‘new’ instance which includes the upgrade of instance type, reboot because of aws downtime, etc. I don’t want it to destroy any existing data. If there is some way to detect if the volume needs to be zero-ed, that would be very helpful.