Re: Handle Leap Seconds with Cassandra

2016-11-03 Thread Eric Stevens
You're able to set the timestamp of the write in the client application. If you have a table which is especially sensitive to out of order writes and want to deal with the repeated second correctly, you could do slewing at your client application layer and be explicit with the timestamp for those s

Re: Handle Leap Seconds with Cassandra

2016-11-02 Thread Ben Bromhead
Based on most of what I've said previously pretty much most ways of avoiding your ordering issue of the leap second is going to be a "hack" and there will be some amount of hope involved. If the updates occur more than 300ms apart and you are confident your nodes have clocks that are within 150ms

Re: Handle Leap Seconds with Cassandra

2016-11-02 Thread Anuj Wadehra
Thanks Ben for taking out time for the detailed reply !! We dont need strict ordering for all operations but we are looking for scenarios where 2 quick updates to same column of same row are possible. By quick updates, I mean >300 ms. Configuring NTP properly (as mentioned in some blogs in your

Re: Handle Leap Seconds with Cassandra

2016-10-27 Thread Ben Bromhead
If you need guaranteed strict ordering in a distributed system, I would not use Cassandra, Cassandra does not provide this out of the box. I would look to a system that uses lamport or vector clocks. Based on your description of how your systems runs at the moment (and how close your updates are to

Re: Handle Leap Seconds with Cassandra

2016-10-27 Thread Edward Capriolo
Following https://issues.apache.org/jira/browse/CASSANDRA-9131. It is very interesting to track how the timestamp has moved from the user, to the server, then back to the user quasi the driver. Next we will be accounting for the earths slowing rotation as the ice caps melt :) https://www.uwgb.edu

Re: Handle Leap Seconds with Cassandra

2016-10-27 Thread Anuj Wadehra
Hi Ben, Thanks for your reply. We dont use timestamps in primary key. We rely on server side timestamps generated by coordinator. So, no functions at client side would help.  Yes, drifts can create problems too. But even if you ensure that nodes are perfectly synced with NTP, you will surely mes

Re: Handle Leap Seconds with Cassandra

2016-10-20 Thread Ben Bromhead
http://www.datastax.com/dev/blog/preparing-for-the-leap-second gives a pretty good overview If you are using a timestamp as part of your primary key, this is the situation where you could end up overwriting data. I would suggest using timeuuid instead which will ensure that you get different prima