[
https://issues.apache.org/jira/browse/MESOS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908890#comment-13908890
]
Benjamin Mahler commented on MESOS-764:
---------------------------------------
Related patches so far:
(1) Initial Registrar: https://reviews.apache.org/r/14383/ (committed)
(2) Injection: https://reviews.apache.org/r/14384/ (committed)
(3) Cleanup from (1): https://reviews.apache.org/r/15099/ (committed)
(4) Registry Format: https://reviews.apache.org/r/18158/
(5) More cleanup: https://reviews.apache.org/r/18341/
I'll also be resurrecting my old patches for recovery, master integration,
upgrading, performance testing.
> 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.1.5#6160)
