[MESOS-884] Incorrect asynchronous detection and contention loops in Master

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.16.0
• Assignee: Yan Xu
• Reporter: Yan Xu
• Created: 17/Dec/13 00:01
• Updated: 19/Dec/13 22:25
• Resolved: 19/Dec/13 22:25

Description

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

MasterContender::contend -> Master::contended -> MasterDetector::detect -> Master::detected
-> Master::lostCandidacy -> MasterContender::contend -> Master::contended -> MasterDetector::detect -> Master::detected

They are not formulated as two separate loops

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

so that it's possible for contended() to produce more detect -> detected -> detect loops when there are existing such loops running.

They should be modeled as two independent closed loops.