You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Yan Xu (JIRA)" <ji...@apache.org> on 2013/12/17 01:02:09 UTC

[jira] [Created] (MESOS-884) Incorrect asynchronous detection and contention loops in Master

Yan Xu created MESOS-884:
----------------------------

             Summary: Incorrect asynchronous detection and contention loops in Master
                 Key: MESOS-884
                 URL: https://issues.apache.org/jira/browse/MESOS-884
             Project: Mesos
          Issue Type: Bug
            Reporter: Yan Xu
             Fix For: 0.16.0


The detection/contention workflow in Master currently works like this:

contend -> contended -> detect -> detected
                                    -> lostCandidacy -> contend -> contended -> detect -> detected

They are not formulated as two separate loops so that it's possible for [contended()|https://github.com/apache/mesos/blob/9cbb81ba4c17b4f6e88ef20d47c9158d0a5ea5c6/src/master/master.cpp#L685] to produce more detect -> detected -> detect loops when there are existing such loops running.

They should be modeled as two independent closed loops.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)