On Tue, Dec 15, 2015 at 2:57 PM Paulo Motta <pauloricard...@gmail.com> wrote:
> What cassandra and driver versions are you running? > > We are using 2.1.7.1 > 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. > > So, we need to look for clock sync issues between nodes in our ring? How close do they need to be? > 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. > > Very cool! If we have multiple nodes in our application, I suppose *their* clocks will have to be sync'ed for this to work, right?
