[
https://issues.apache.org/jira/browse/CASSANDRA-11991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344227#comment-15344227
]
Jason Brown commented on CASSANDRA-11991:
-----------------------------------------
bq. I think having our CQL clock strictly monotonic per-node (rather than
per-connection) is cleaner and less surprising to people.
ok, I'll buy that.
Otherwise, +1 on all branches. I checked out the test results, and the ones
that failed were either 1) unrelated to this CAS change or 2) test timeouts
(and still unrelated to CAS).
> 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)
