I was considering that when bootstrapping starts the nodes receive writes so
that when the process is complete they have both the data from the streaming
process and all writes from the time they started. So that a repair is not
needed. Compared to bootstrapping a node from a backup where a (non
On Fri, May 17, 2013 at 11:13 AM, aaron morton wrote:
> Bootstrapping a new node into the cluster has a small impact on the existing
> nodes and the new nodes to have all the data they need when the finish the
> process.
Sorry for the pedantry, but bootstrapping from existing replicas
cannot guar
> b) do people skip backups altogether except for huge outages and just let
> rebooted server instances come up empty to repopulate via C*?
This one.
Bootstrapping a new node into the cluster has a small impact on the existing
nodes and the new nodes to have all the data they need when the fini
On May 16, 2013, at 17:05 , Brian Tarbox wrote:
> An alternative that we had explored for a while was to do a two stage backup:
> 1) copy a C* snapshot from the ephemeral drive to an EBS drive
> 2) do an EBS snapshot to S3.
>
> The idea being that EBS is quite reliable, S3 is still the emergency
>From this list and the NYC* conference it seems that the consensus
configuration of C* on EC2 is to put the data on an ephemeral drive and
then periodically back it the drive to S3...relying on C*'s inherent fault
tolerance to deal with any data loss.
Fine, and we're doing this...but we find that
