incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan King <r...@twitter.com>
Subject Re: internal ntp
Date Fri, 17 Jun 2011 16:52:37 GMT
There's more burden on the user, but with a benefit– client supplied
timestamps mean that client retries are idempotent as long as they use
the same timestamp.*

-ryan

* doesn't apply to counters

On Fri, Jun 17, 2011 at 8:01 AM, Tim Wisniewski <tjw3000@gmail.com> wrote:
> it's slightly less burden on the user
>
> On Fri, Jun 17, 2011 at 11:00 AM, Gary Dusbabek <gdusbabek@gmail.com> wrote:
>
>> That problem is already solved externally.  I don't see the value of
>> reimplementing it inside of cassandra.
>>
>> Gary.
>>
>> On Fri, Jun 17, 2011 at 09:58, Tim Wisniewski <tjw3000@gmail.com> wrote:
>> > Hi,
>> >
>> > My understanding is data corruption can occur if the node clocks are too
>> far
>> > out of sync.  What if Cassandra nodes maintained an internal time sync
>> via
>> > ntp or something?
>> >
>> > -Tim
>> >
>>
>

Mime
View raw message