incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikhail Tsaplin <>
Subject Handling quorum writies fails
Date Sat, 10 Aug 2013 16:13:09 GMT

According to Datastax documentation about atomicity in Cassandra: QUORUM
write succeeded only on one node will not be rolled back (Check Atomicity
chapter there:
So when I am performing a QUORUM write on cluster with RF=3 and one node
fails, I will get write error status and one successful write on another
node. This produces two cases:

   1. write will be propagated to other nodes when they became online;
   2. write can be completely lost if the node accepted that write will be
   completely broken before propagation.

What is the best ways to deal with such kind of fails in let say
hypothetical funds transfer logging?

View raw message