What cassandra and driver versions are you running? It may be that the second update is getting the same timestamp as the first, or even a lower timestamp if it's being processed by another server with unsynced clock, so that update may be getting lost.
If you have high frequency updates in the same partition from the same client you should probably use client-side timestamps with a configured timestamp generator on the driver, available in Cassandra 2.1 and Java driver 2.1.2, and default in java driver 3.0. For more information: - http://www.datastax.com/dev/blog/java-driver-2-1-2-native-protocol-v3 - https://datastax.github.io/java-driver/features/query_timestamps/ - https://docs.datastax.com/en/developer/cpp-driver/2.1/cpp-driver/reference/clientsideTimestamps.html 2015-12-15 11:36 GMT-08:00 James Carman <ja...@carmanconsulting.com>: > We are encountering a situation in our environment (a 6-node Cassandra > ring) where we are trying to insert a row and then immediately update it, > using LOCAL_QUORUM consistency (replication factor = 3). I have replicated > the issue using the following code: > > https://gist.github.com/jwcarman/72714e6d0ea3508e24cc > > Should we expect this to work? Should LOCAL_QUORUM be sufficient? If so, > what type of setup issues would we look for which would cause these types > of issues? > > Thanks, > > James >
