oftentimes people use time actually subconsciously to express causal
relations ("before/after"), as long as you have some other means to
establish causal relations, you don't really need to have an exactly clock.On Mon, Jun 27, 2011 at 4:54 PM, aaron morton <aa...@thelastpickle.com>wrote: > Without exception the timestamp is set by the client, not the server. The > one exception to the without exception rule is CounterColumnType operations. > > If you are in a situation where you need better timing than you can get > with ntp you should try to design around it. > > Hope that helps. > ----------------- > Aaron Morton > Freelance Cassandra Developer > @aaronmorton > http://www.thelastpickle.com > > On 28 Jun 2011, at 10:03, A J wrote: > > > During writes, the timestamp field in the column is the system-time of > > that node (correct me if that is not the case and the system-time of > > the co-ordinator is what gets applied to all the replicas). > > During reads, the latest write wins. > > > > What if there is a clock skew ? It could lead to a stale write > > over-riding the actual latest write, just because the clock of that > > node is ahead of the other node. Right ? > >
