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

Handle a temporary one-way slave --> master socket closure.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Accepted
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • agent
    • None

    Description

      In the same spirit as MESOS-1668, we want to correctly handle a scenario where the slave --> master socket closes, and a new socket can be immediately re-established.

      If this occurs, the ping / pongs will resume but there may be dropped messages sent by the slave, and so a re-registration would be a good safety net.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MESOS-1529 Handle a network partition between Master and Slave

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. MESOS-1668 Handle a temporary one-way master --> slave socket closure.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          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
              bmahler Benjamin Mahler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: