; >>>>>> > There are bunch of
> >>>>>> issues w.r.t to
> >>>>>> synchronization of clocks
reported by our devops :)
>>>>>> >
>>>>>> > we have multiple clients
>>>>>> (for example bunch of
>>>>>>
02/09/2017 06:47 PM, Kant Kodali wrote:
>> > Hi Justin,
>> >
>> > There are bunch of issues w.r.t to synchronization of clocks when we
>> > used ntpd. Also the time it took to sync the clocks was approx 140ms
>> > (don't quote me on it though because it is re
gt; Thanks!
> >
> >
> > On Thu, Feb 9, 2017 at 4:16 PM, Justin Cameron <jus...@instaclustr.com
> > <mailto:jus...@instaclustr.com>> wrote:
> >
> > Hi Kant,
> >
> > Clock synchronization is important - you should ensure that ntpd is
>>> And it clearly says Linearizable consistency can be
>>>>>>>>>>>> achieved with LWT's. so should I assume the
>>>>>>>>>>>> Linearizability in the context of the above article is
>>>>>>>>>&
es. If your particular use case is
> > especially sensitive to out-of-order mutations it is possible to set
> > timestamps on the client side using the
> > drivers. https://docs.datastax.com/en/d
> eveloper/java-driver/3.1/manual/query_timestamps/
> > <htt
ogleusercontent.com/media/research.google.com/en//archive/spanner-osdi2012.pdf?
>>>>>>>>>> Actually I never heard of setting up GPS modules and how that
>>>>>>>>>> can be helpful. Let me research on that but good point.
>>>>>>>>>>
especially sensitive to out-of-order mutations it is possible to set
> > timestamps on the client side using the
> > drivers. https://docs.datastax.com/en/d
> eveloper/java-driver/3.1/manual/query_timestamps/
> > <https://docs.datastax.com/en/developer/java-driver/3.1/man
ould suggest
>>>>>>>>> that was a
>>>>>>>>> poor choice of upstream (probably stratum 2 or 3) source.
>>>>>>>>>
>>>>>>>>> As Jonathan mentioned, there's no guarantee from Cassandra,
>>>>>>>>&g
6 PM, Justin Cameron <jus...@instaclustr.com
>> > <mailto:jus...@instaclustr.com>> wrote:
>> >
>> > Hi Kant,
>> >
>> > Clock synchronization is important - you should ensure that ntpd is
>> > properly configured on all nodes. If your
properly configured on all nodes. If your particular use case is
> > especially sensitive to out-of-order mutations it is possible to set
> > timestamps on the client side using the
> > drivers. https://docs.datastax.com/en/d
> eveloper/java-driver/3.1/manual/query_timestam
k to sync the clocks
>>>>>> > was approx 140ms (don't quote me on it though because it is
>>>>>> > reported by our devops :)
>>>>>> >
>>>>>> > we have multiple clients (for example bunch of micro services
&
gt;>>> jus...@instaclustr.com
>>>> > <mailto:jus...@instaclustr.com>> wrote:
>>>> >
>>>> > Hi Kant,
>>>> >
>>>> > Clock synchronization is important - you should ensure that ntpd
>>>> is
>>
tion is important - you should ensure that ntpd is
>>> > properly configured on all nodes. If your particular use case is
>>> > especially sensitive to out-of-order mutations it is possible to
>>> set
>>> > timestamps on the
> <https://docs.datastax.com/en/developer/java-driver/3.1/m
>> anual/query_timestamps/>
>> >
>> > We use our own NTP cluster to reduce clock drift as much as
>> > possible, but public NTP servers are good enough for most
>> > uses. https://www.i
pache-cassandra-synchronization/
> >
> > <https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/>
> >
> > <https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/
> >
> > <https://www.instaclust
cassandra-synchronization/>
> >
> <https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/
>
> <https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/>>
> >
> > Cheers,
> >
are good enough for most
> > uses. https://www.instaclustr.com/blog/2015/11/05/apache-
> cassandra-synchronization/
> > <https://www.instaclustr.com/blog/2015/11/05/apache-
> cassandra-synchronization/>
> >
> > Cheers,
> > Justin
> >
> >
/11/05/apache-cassandra-synchronization/>
>
> Cheers,
> Justin
>
> On Thu, 9 Feb 2017 at 16:09 Kant Kodali <k...@peernova.com
> <mailto:k...@peernova.com>> wrote:
>
> How does Cassandra achieve Linearizability with “Last write
>
drift as much as possible, but
> public NTP servers are good enough for most uses.
> https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/
>
> Cheers,
> Justin
>
> On Thu, 9 Feb 2017 at 16:09 Kant Kodali <k...@peernova.com> wrote:
>
> How does Cassand
It doesn't, nor does it claim to.
On Thu, Feb 9, 2017 at 4:09 PM Kant Kodali <k...@peernova.com> wrote:
> How does Cassandra achieve Linearizability with “Last write wins”
> (conflict resolution methods based on time-of-day clocks) ?
>
> Relying on synchronized clocks are al
hu, 9 Feb 2017 at 16:09 Kant Kodali <k...@peernova.com> wrote:
>
>> How does Cassandra achieve Linearizability with “Last write wins”
>> (conflict resolution methods based on time-of-day clocks) ?
>>
>> Relying on synchronized clocks are almost certainly non-line
Kodali <k...@peernova.com> wrote:
> How does Cassandra achieve Linearizability with “Last write wins”
> (conflict resolution methods based on time-of-day clocks) ?
>
> Relying on synchronized clocks are almost certainly non-linearizable,
> because clock timestamps cannot be guaran
How does Cassandra achieve Linearizability with “Last write wins” (conflict
resolution methods based on time-of-day clocks) ?
Relying on synchronized clocks are almost certainly non-linearizable,
because clock timestamps cannot be guaranteed to be consistent with actual
event ordering due
24 matches
Mail list logo
