Cassandra's "Repair" Should Be Called "Required Maintenance" | Big Data Nerd

Cassandra’s “Repair” Should Be Called “Required Maintenance” | Big Data Nerd

Cassandra’s “Repair” Should Be Called “Required Maintenance” Posted by Ryan Svihla on September 25, 2015 One of the bigger challenges when you go Eventually Consistent is how to reconcile data not being replicated. This happens if your using Oracle and multi-data centers with tech like Golden Gate and it happens if you’re using async replicas with MySQL and one of your replicas got out of whack. You need a way to “repair” the lost data. Since Cassandra fully embraces eventually consistency repair is actually a important mechanism for making sure copies of data are shipped around the cluster to meet your specified replication factor. About now several of you have alarm bells going off and think I’m insane. Let’s step through the common objections I hear. What about Consistency Level?

Read full article from Cassandra’s “Repair” Should Be Called “Required Maintenance” | Big Data Nerd