If you are worried about the server side time drift (which usually should not be a problem, right?) then you can also generate the timestamp on the client side if that clock is more accurate. That probably should do it if you can do that.

If you think that server clock drift will cause you problems (first write "overwriting" the second because the timestamp of the first write is in the future compared to the second one because of the clock drift), then maybe the TokenAwarePolicy will help you. At least writes on the same key should have the same timestamp (from the same coordinator) as long as the coordinators are all up and running smoothly.

Normally you can have full consistency by doing CL=QUORUM reads and CL=QUORUM writes. That way you have high availability and faster reads than in CL=ALL case. No matter what the consistency level is, you can get wrong results if writes get serialized in wrong order because of the clock drift.

Interesting topic. Are there other ways to handle that, anyone?


2013/12/31 Ryan, Brent <BRyan@cvent.com>
Thanks Hannu!

I wasnít aware of the TokenAwarePolicy and thatís exactly what I was talking about so Iíll give that a try. †Because setting the consistency level doesnít really work unless I set it to ALL, but I really donít want to pay that sort of performance penalty. †Iíd rather stick with QUORUM writes and use the TokenAwarePolicy which should avoid situations where RowKey X can be written to replication node 1 for request 1 and then written to replication node 2 for request 2. †This normally isnít an issue unless the time drift across the cluster > the time between 2 writes for the same row key.


From: Hannu KrŲger <hkroger@gmail.com>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Tuesday, December 31, 2013 at 9:15 AM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re: Cassandra client alternatives to mimic Couchbase sharding ???


DataStax Cassandra Java Driver has the possibility to choose the coordinator node based on the partition key (TokenAwarePolicy), however that probably does not solve the consistency problem you are thinking about:

If you really want to have full consistency, you should read this and tune consitency level accordingly if you haven't already:


2013/12/31 Ryan, Brent <BRyan@cvent.com>
Assuming that you have a 3 node cassandra cluster with replication factor of 3 (so all nodes have the data)Ö

Does there exist a cassandra client that would allow a cassandra cluster to behave similarly to a couchbase cluster where for a given RowKey X, the client would always communicate to the same node in the cassandra cluster? †Essentially provides sharding at the client tier by RowKey. †The main reason for doing this would be to avoid some of the issues you run into with eventual consistency and allowing the cluster to resolve conflicts using server side timestamps?

Iím not sure exactly if this would work like Iíd want, but thought it might be an interesting use case. †You might even be able to extend this behavior into the client further if the client is aware of the sharding algorithm being applied to the cluster so that you always communicate to a shard that has the data for a given row key.