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

MesosClusterScheduler reads options from dispatcher conf instead of submission conf

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.3.0, 2.3.1, 2.3.2, 2.4.0
    • Fix Version/s: 2.4.4, 3.0.0
    • Component/s: Mesos
    • Labels:
      None

      Description

      There is at least one option accessed in MesosClusterScheduler that should come from the submission's configuration instead of the dispatcher's:

      spark.mesos.fetcherCache.enable

      Coincidentally, the spark.mesos.fetcherCache.enable option was previously misnamed, as referenced in the linked JIRA.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mwlon Martin Loncaric
                Reporter:
                mwlon Martin Loncaric
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: