Hello, Based on what I've read in the archives here and on the documentation on Datastax and the Cassandra Community, EBS volumes, even provisioned IOPS with EBS optimized instances, are not recommended due to inconsistent performance. This I can deal with, but I was hoping for some recommendations from the community as far as solutions for data safety.
I have a few ideas in mind: 1. Instance store for the database, then cassandra snapshots (via nodetool), stored on an EBS provisioned IOPS volume attached to the instance. That volume would serve to keep the DB safe in case of instance downtime, and I would set up regular snapshotting on the EBS volume for data safety (pushed to S3 and eventually glacier) 2. Instance store used as a bcache write-through cache for attached EBS volumes. The attached volumes persist all writes and are again snapshotted regularly. 3. Using a backup system, either manually via rsync or through something like Priam, to directly push backups of the data on ephemeral storage to S3. >From where I'm sitting, #2 seems the easiest to set up, but could potentially cause problems if the EBS volume backing writes sees a spike in latency, driving up write times even if read times would remain fairly consistent. Do any of you all have recommendations or suggestions for a system like this? Thanks in advance! --Bryan
