Details
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
- is related to
-
SPARK-26082 Misnaming of spark.mesos.fetch(er)Cache.enable in MesosClusterScheduler
- Resolved
- links to
This is resolved via https://github.com/apache/spark/pull/23924 .