[
https://issues.apache.org/jira/browse/CASSANDRA-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150875#comment-14150875
]
Blake Eggleston commented on CASSANDRA-6246:
--------------------------------------------
Making switching to a special hybrid mode a required step could be error prone.
Plus, the direction your transitioning is important. That's really the tricky
part, running serialized queries while the cluster transparently transitions
from one protocol to another. Specifically when the nodes for a given range can
and do switch. Making it configurable could be useful, at least from a peace of
mind / opt-in perspective. We'd have to work out how to transition back from
epaxos to old paxos though.
> EPaxos
> ------
>
> Key: CASSANDRA-6246
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6246
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Blake Eggleston
> Priority: Minor
>
> One reason we haven't optimized our Paxos implementation with Multi-paxos is
> that Multi-paxos requires leader election and hence, a period of
> unavailability when the leader dies.
> EPaxos is a Paxos variant that requires (1) less messages than multi-paxos,
> (2) is particularly useful across multiple datacenters, and (3) allows any
> node to act as coordinator:
> http://sigops.org/sosp/sosp13/papers/p358-moraru.pdf
> However, there is substantial additional complexity involved if we choose to
> implement it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
