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

Default executor exits with a stack trace in a few scenarios.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 1.2.0
    • None

    Description

      This happened due to MESOS-6296 accidentally making the 1.2 release. In some scenarios, the default executor commits suicide (as expected) but does it with a stack trace due to a failed invariant check.

      The error scenarios happen when some task(s) in the task group terminated successfully, and if the other task(s) thereafter either were killed or terminated with a non-zero status code.

      e.g., Task 1 terminated with status 0 , Task 2 was killed by the scheduler. In this scenario, the default executor would commit suicide with a stack trace.

      Attachments

        Activity

          People

            anandmazumdar Anand Mazumdar
            anandmazumdar Anand Mazumdar
            Vinod Kone Vinod Kone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: