Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-884

Incorrect asynchronous detection and contention loops in Master

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.16.0
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              xujyan Yan Xu
              Reporter:
              xujyan Yan Xu
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: