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

Improve the logic of orphan tasks

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • None
    • None
    • Mesosphere Sprint 38
    • 5

    Description

      Right now, a task is called orphaned if an agent re-registers with it but the corresponding framework information is not known to the master. This happens immediately after a master failover.

      It would great if the master knows the information about the framework even after a failover, irrespective of whether a framework re-registers, so that we don't have orphan tasks. Getting rid of orphan tasks will make the task authorization story easy (see MESOS-5757).

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MESOS-4659 Avoid leaving orphan task after framework failure + master failover

          • Major - Major loss of function.
          • Accepted
          is related to

          Task - A task that needs to be done. MESOS-1719 Master should persist framework information

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

          Bug - A problem which impairs or prevents the functions of the product. MESOS-5757 Authorize orphaned tasks

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              vinodkone Vinod Kone
              js84 Jörg Schad
              Anand Mazumdar Anand Mazumdar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: