cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Meyer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6246) EPaxos
Date Thu, 29 Oct 2015 15:29:28 GMT

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

Jim Meyer commented on CASSANDRA-6246:
--------------------------------------

Does anyone know if this patch will help with CASSANDRA-9328 (i.e. outcome of LWT not reported
to client when there is contention).  There's a suggestion to that effect in the comments
of 9328, but I don't know if anyone has tried running the test code in 9328 to see if this
patch has an effect on that issue.

Is this patch compatible with rc2 of Cassandra 3.0.0 or does it need to be updated?  When
is it planned to add epaxos to an official build?  Thanks for any info.

> EPaxos
> ------
>
>                 Key: CASSANDRA-6246
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6246
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Blake Eggleston
>             Fix For: 3.x
>
>
> 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)

Mime
View raw message