You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/03/03 20:54:26 UTC
[jira] [Commented] (MESOS-764) Implement Master persistence using
the Registrar.
[ https://issues.apache.org/jira/browse/MESOS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918512#comment-13918512 ]
Benjamin Mahler commented on MESOS-764:
---------------------------------------
(6) Forcing a version change during recovery: https://reviews.apache.org/r/18675/
> Implement Master persistence using the Registrar.
> -------------------------------------------------
>
> Key: MESOS-764
> URL: https://issues.apache.org/jira/browse/MESOS-764
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Benjamin Mahler
> Assignee: Benjamin Mahler
> Labels: twitter
> Fix For: 0.19.0
>
>
> Design document:
> https://cwiki.apache.org/confluence/display/MESOS/Registrar+Design+Document
> Using the registrar as a means for persistent, highly available storage of the slave information will allow us to recover slave information when a master is elected as a leader.
> Having persistent slave information will allow the master to answer reconciliation requests from frameworks in a correct and reliable manner. There are currently cases where we cannot answer reconciliation requests in order to avoid providing an incorrect answer (hints in MESOS-295).
> It will also ensure that when we inform the world that a slave is removed, we can enforce that as truth even with the presence of dropped messages and master failovers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)