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

Scheduler::disconnected() should be called when the single master fails

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • master
    • None

    Description

      According to the comments in "scheduler.hpp", "sched.cpp" and also common sense, the Scheduler::disconnected() callback should be also invoked when master fails. However, in case of StandaloneMasterDetector this won't happen, since it doesn't track master failures. Though the StandaloneMasterDetector is not intended for production use, we should update it so that framework authors observe consistent behaviour and can test their frameworks in a single-master setup.

      As a short-term fix we may want to update comments in "scheduler.hpp" and "sched.cpp" for clarity.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. MESOS-5180 Scheduler driver does not detect disconnection with master and reregister.

          • Major - Major loss of function.
          • Accepted
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-887 Scheduler driver should use exited() to detect disconnection with Master.

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-1963 Slave should use exited() to detect disconnection with Master.

          • Major - Major loss of function.
          • Accepted

          Activity

            People

              Unassigned Unassigned
              alexr Alex R
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: