[
https://issues.apache.org/jira/browse/MESOS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797326#comment-13797326
]
Jie Yu edited comment on MESOS-736 at 10/25/13 7:20 PM:
--------------------------------------------------------
Second patch:
https://reviews.apache.org/r/14902/
was (Author: jieyu):
Second patch:
https://reviews.apache.org/r/14686/
> 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)
