cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11991) On clock skew, paxos may "corrupt" the node clock
Date Tue, 21 Jun 2016 22:53:57 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342972#comment-15342972
] 

Jason Brown commented on CASSANDRA-11991:
-----------------------------------------

lgtm. The only minor nit I have is CASSANDRA-9649 made {{ClientState#lastTimestampMicros}}
a static field. I believe this change helped accelerate the cluster get into a bad state wrt
the propagation of bad timestamps. wdyt about switching it back to being an instance field
(not static)?

> On clock skew, paxos may "corrupt" the node clock
> -------------------------------------------------
>
>                 Key: CASSANDRA-11991
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11991
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> W made a mistake in CASSANDRA-9649 so that a temporal clock skew on one node can "corrupt"
other node clocks through Paxos. That wasn't intended and we should fix that. I'll attach
a patch later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message