Do data persist on Instance store when rebooting an instance on Amazon EC2?

[kporter]

@mlabour

Please can you confirm that the AMI found here: Install on Amazon EC2 | Aerospike Documentation is EBS backed?

I think AMIs are EBS agnostic.

@mlabour

case a. I would not use EBS at all. I would use the ephemeral Instance Stores. I would spawn multiple machines with replication factor to protect against a machine going down and data loss.

You do run the risk of losing data if multiple nodes fail. This exists on bare-metal but on bare-metal the are more situations where the data can still be recovered but would be lost on ephemeral.

@mlabour

case b. Use the bcache https://www.aerospike.com/docs/operations/plan/ssd/bcache/. But it seems there is still a pending bug.

Yes, bcache as been problematic for us. Aerospike 3.5.10 I believe is expected to be out next week will include a new feature for defining a shadow disk. Basically writes will go to the primary disk and the shadow disk, reads will only go to the primary. So stay tuned .

@mlabour

case c. Turn the Instance Stores into EBS. Data would be persisted so I wouldn’t have to have a replication factor if i can afford a down time. But I am concerned about read latency.

Depends on how often EBS volumes fail. Also means that if a node were to fail, your cluster will be missing data till you are able to replace it with another node with the appropriate EBS volume.