cassandra-commits mailing list archives

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

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

Blake Eggleston commented on CASSANDRA-6246:
--------------------------------------------

bq. Does anyone know if this patch will help with CASSANDRA-9328

it should, yes

bq. Is this patch compatible with rc2 of Cassandra 3.0.0 or does it need to be updated?

it needs to be rebased onto cassandra-3.0, there are a few parts where it interacts directly
with the cell timestamps

bq. When is it planned to add epaxos to an official build?

There are no plans at the moment, the patch still needs to be reviewed.

> 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