[
https://issues.apache.org/jira/browse/MESOS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874248#comment-13874248
]
Jie Yu commented on MESOS-736:
------------------------------
Here are the final set of patches:
https://reviews.apache.org/r/14631/
https://reviews.apache.org/r/14902/
https://reviews.apache.org/r/15802/
https://reviews.apache.org/r/16433/
https://reviews.apache.org/r/16946/
https://reviews.apache.org/r/16064/
https://reviews.apache.org/r/16065/
https://reviews.apache.org/r/16982/
> Support catch-up replicated log
> -------------------------------
>
> Key: MESOS-736
> URL: https://issues.apache.org/jira/browse/MESOS-736
> Project: Mesos
> Issue Type: Improvement
> Components: replicated log
> Reporter: Jie Yu
> Assignee: Jie Yu
> Labels: twitter
> Fix For: 0.16.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.5#6160)
