You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2013/10/14 21:06:41 UTC

[jira] [Commented] (MESOS-736) Support catch-up replicated log

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

Jie Yu commented on MESOS-736:
------------------------------

First patch:
https://reviews.apache.org/r/14631/

> Support catch-up replicated log
> -------------------------------
>
>                 Key: MESOS-736
>                 URL: https://issues.apache.org/jira/browse/MESOS-736
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Jie Yu
>            Assignee: Jie Yu
>              Labels: features
>             Fix For: 0.15.0
>
>
> When a replica joins Paxos with an empty log, we don't allow this replica to fully participate in Paxos immediately. Instead, this replica is treated as a non-voting member, meaning that it will not reply to any requests from other replicas. It simply learns those log entries that have been agreed on and tries to catch up the leader. When the catch-up process is done, we re-admit this replica to Paxos and allow it to vote.
> If we have a disk failure and want to swap a master machine, we can simply start the scheduler on a new machine with an empty log (and that's it).



--
This message was sent by Atlassian JIRA
(v6.1#6144)