[
https://issues.apache.org/jira/browse/CASSANDRA-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718473#comment-13718473
]
Sylvain Lebresne commented on CASSANDRA-5797:
---------------------------------------------
bq. although I think it would be better to come up w/ a different enum for the
Paxos phases than re-use CL
The thing is that for reads, we must have SERIAL and LOCAL_SERIAL in CL if we
want thrift to support it. So once we have them in CL, is it really worth
adding a separate enum for the write case? (honest question, I'm fine doing it,
just wonder if it's worth bothering since things will be mixed up for reads
anyway).
> 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
