Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-15359

Mesos dispatcher should handle DRIVER_ABORTED status from mesosDriver.run()

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Incomplete
    • None
    • None
    • Deploy, Mesos

    Description

      Mesos dispatcher handles DRIVER_ABORTED status for mesosDriver.run() during the successful registration but if the mesosDriver.run() returns DRIVER_ABORTED status after the successful register then there is no action for the status and the thread will be terminated.

      I think we need to throw the exception and shutdown the dispatcher.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SPARK-15142 Spark Mesos dispatcher becomes unusable when the Mesos master restarts

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

          Bug - A problem which impairs or prevents the functions of the product. SPARK-24641 Spark-Mesos integration doesn't respect request to abort itself

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

          Improvement - An improvement or enhancement to an existing feature or task. SPARK-15288 Mesos dispatcher should handle gracefully when any thread gets UncaughtException

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

          Pull request #13143 [Github] Pull Request #13143 (devaraj-kavali)

          Activity

            People

              Unassigned Unassigned
              devaraj Devaraj Kavali
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: