Hi all, We are evaluating Cassandra for a geographically distributed deployment that requires multi master replication.
We have a few questions regarding how replication is handled in Cassandra, like: 1. Which mechanism is used to replicate the changes from one system to another: statement distribution or recording the changeset via triggers or storing the changeset in transaction log? 2. Since replication is continuous copying of changes from one node to another, these changes would have to be snapshotted in order to sustain temporary network failures so that replication can resume after the network problem is healed. is there a mechanism to define how long we can store/archive the snaphotted changes before we discard and would demand a recreation of node from the scratch rather than rejoin 3. What options are available for conflict resolution since we are talking about master-master replication across tens of nodes? 4. If a node is rejoined after a split network where same records would have been modified on multiple nodes, is there a mechanism to merge the data, resolve conflicts and eventually reach to a consistent state? Thanks and Regards, Samba
