I suppose you could use rsync (sstable files are immutable, so you don't need to worry about not getting a "consistent" version of the data files), but compared to letting Cassandra handle the replication the way it's designed to,
# you'll generate a lot of disk i/o doing that vs # your backup cluster will miss a relatively large amount of the most recent updates # your failover process will be more error-prone On Mon, May 3, 2010 at 8:05 AM, Viktor Jevdokimov <viktor.jevdoki...@adform.com> wrote: > Hello, > > Our system (not Cassandra) have backup cluster in different datacenter in > case of primary cluster unavailability or for software upgrades. > 100% of traffic goes to primary cluster. We switch 100% traffic to backup > cluster in case above for a short time, then when issues are resolved, > traffic is switched back to primary. > > We'd like to have primary and backup Cassandra clusters in different > datacenters for the same reasons. > We do not want to have a high traffic between primary and backup datacenters. > > Now the questions: > > 1. How to sync Cassandra clusters (backup<->primary) with minimal traffic? > 2. How to configure Cassandra in such case? > > > Thanks, > > Viktor > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
