[
https://issues.apache.org/jira/browse/CASSANDRA-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718549#comment-13718549
]
Sylvain Lebresne commented on CASSANDRA-5797:
---------------------------------------------
bq. I like LOCAL_SERIAL over ANY
I think there is some confusion. The suggestion of CL.ANY was for the commit
part of Paxos. That part is basically a standard write (that happens after the
paxos algorithm has unfolded but does impact the visibility of the CAS write by
non-serial reads). For that, LOCAL_SERIAL don't really make sense imo (it's
"wrong" even). ANY does is what match the most what happens, because you are
guaranteed the write is replicated somewhere (paxos ensures that) but you may
not be able to see your write right away with normal reads, even at CL.ALL
(which is also something that CL.ANY).
> DC-local CAS
> ------------
>
> Key: CASSANDRA-5797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5797
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 2.0
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.0.1
>
>
> For two-datacenter deployments where the second DC is strictly for disaster
> failover, it would be useful to restrict CAS to a single DC to avoid cross-DC
> round trips.
> (This would require manually truncating {{system.paxos}} when failing over.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
