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

Issues with driver re-starting on mesos (supervise)

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.0
    • Fix Version/s: 2.3.0
    • Component/s: Mesos
    • Labels:
      None

      Description

      There are two issues with driver re-starting on mesos using the supervise flag:

      • We need to add spark.mesos.driver.frameworkId to the reloaded properties for checkpointing, otherwise the new frameworkId propagated by the dispatcher will be overwritten by the checkpointed data.
      • Unique driver task ids are not used by the dispatcher:
        https://issues.apache.org/jira/browse/MESOS-4737
        https://issues.apache.org/jira/browse/MESOS-3070
        This issue is the same in principle as in the case with standalone mode where the master needs to re-launch drivers with a new appId (driverId) to deal with net partitions.

        Attachments

          Activity

            People

            • Assignee:
              skonto Stavros Kontopoulos
              Reporter:
              skonto Stavros Kontopoulos
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: