No experience doing it that way personally, but I'm curious: Are you backing up in case of ephemeral instance dying, or backing up in case of data problems / errors / etc?
On instance dying, you're probably fine with just straight normal replacements, not restoring from backup. For the rest, is it cheaper to use something like tablesnap and go straight to s3? On Thu, Dec 5, 2019 at 12:21 PM Carl Mueller <carl.muel...@smartthings.com.invalid> wrote: > Does anyone have experience tooling written to support this strategy: > > Use case: run cassandra on i3 instances on ephemerals but synchronize the > sstables and commitlog files to the cheapest EBS volume type (those have > bad IOPS but decent enough throughput) > > On node replace, the startup script for the node, back-copies the sstables > and commitlog state from the EBS to the ephemeral. > > As can be seen: > https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html > > the (presumably) spinning rust tops out at 2375 MB/sec (using multiple EBS > volumes presumably) that would incur about a ten minute delay for node > replacement for a 1TB node, but I imagine this would only be used on higher > IOPS r/w nodes with smaller densities, so 100GB would be about a minute of > delay only, already within the timeframes of an AWS node > replacement/instance restart. > > >
