mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-884) Incorrect asynchronous detection and contention loops in Master
Date Tue, 17 Dec 2013 00:13:08 GMT

     [ https://issues.apache.org/jira/browse/MESOS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yan Xu updated MESOS-884:
-------------------------

    Description: 
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 

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

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.

  was:
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.


> 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
>            Assignee: 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 
> contend -> contended -> lostCandidacy -> contend
> detect -> detected -> detect
> 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)

Mime
View raw message