mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <>
Subject [jira] [Commented] (MESOS-422) Master leader election should be more robust to stale ephemeral nodes
Date Wed, 13 Nov 2013 18:55:21 GMT


Bill Farner commented on MESOS-422:

Instead of generating your own UUID, can you instead rely on the sequential ID provided by
ZooKeeper?  Since your nodes appear to be created with the {{ZOO_SEQUENCE}} flag, you can
count on the node name to be unique.

> Master leader election should be more robust to stale ephemeral nodes
> ---------------------------------------------------------------------
>                 Key: MESOS-422
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0
>            Reporter: Bill Farner
>            Assignee: Yan Xu
>            Priority: Minor
>              Labels: twitter
>             Fix For: 0.16.0
> 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:
> ZK leader election recipe, for reference:

This message was sent by Atlassian JIRA

View raw message