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 2013/05/09 00:37:16 UTC
[jira] [Assigned] (MESOS-422) Master leader election should be more
robust to stale ephemeral nodes
[ https://issues.apache.org/jira/browse/MESOS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler reassigned MESOS-422:
-------------------------------------
Assignee: Benjamin Mahler
> Master leader election should be more robust to stale ephemeral nodes
> ---------------------------------------------------------------------
>
> Key: MESOS-422
> URL: https://issues.apache.org/jira/browse/MESOS-422
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Bill Farner
> Assignee: Benjamin Mahler
> Priority: Minor
>
> When a leading master exits abruptly, it may fatefully restart and think it's the leader. If particularly unlucky, this could result in a set of masters that are indefinitely unstable.
> Sequence of events:
> - Master process becomes leader
> - Master process exits, session expiration counter begins
> - Master process restarts, reads leader node contents, and decides it's the leader (based on PID equality)
> - Previous master session expires, node is deleted
> - Master decides a different master is leader, commits suicide
> - Rinse, repeat for newly-created master node
> The salient fact here is that leaders should be concerned with "did i create the leader node" (ignoring node data) while clients want to be apprised of leader's node data.
> Relevant code:
> https://github.com/apache/mesos/blob/trunk/src/detector/detector.cpp#L548
> ZK leader election recipe, for reference:
> http://zookeeper.apache.org/doc/trunk/recipes.html#sc_leaderElection
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira