Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 6 Jan 2015 09:43:36 +0000 (UTC)
From: "sankalp kohli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12675931.1382757350000.18008.1420537416847@Atlassian.JIRA>
In-Reply-To: <JIRA.12675931.1382757350000@Atlassian.JIRA>
References: <JIRA.12675931.1382757350000@Atlassian.JIRA>
 <JIRA.12675931.1382757350929@arcas>
Subject: [jira] [Commented] (CASSANDRA-6246) EPaxos
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sankalp kohli commented on CASSANDRA-6246:
------------------------------------------

I am a little confused as in how you will use epoch to make sure instances are executed on all replicas when incrementing? 

> 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)