If you are reading at QUOURM there is no problem, this is how eventual
consistency works in Cassandra.
The coordinator will resolve the differences between and the column with the
higher timestamp will win.
If the delete was applied to less then CL nodes the client should have received
a
*Background*: My application is running on a cluster system(which have 4
nodes), and system time of these four nodes are synchronizing by NTP. I use
Write.QUORUM and Read.QUORUM strategy. The probability of this problem is
not very high. Cassandra version is 1.0.3, I have tried Cassandra 1.1.1,
