Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-6966

Removed the calling of suicide() when disconnected() was called by the driver

    Details

    • Type: Task
    • Status: Resolved
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      I don't think that suicide() should be called in the case of a disconnected event. As this will be called when the driver detects a disconnection from the master. When a new master is detected registered() is called by the driver and Marathon continues happily along its way.

      I noticed these issues because Marathon was committing suicide when there were long running network issues between Marathon and the Mesos master.

      All I did with this commit is remove the suicide() call and added a little documentation from the Mesos docs.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              GitHub_marc-barry Marc Barry (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: