You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2019/03/04 20:14:00 UTC
[jira] [Resolved] (SPARK-26192) MesosClusterScheduler reads options
from dispatcher conf instead of submission conf
[ https://issues.apache.org/jira/browse/SPARK-26192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved SPARK-26192.
-----------------------------------
Resolution: Fixed
Assignee: Martin Loncaric
Fix Version/s: (was: 2.3.4)
(was: 2.4.1)
This is resolved via https://github.com/apache/spark/pull/23924 .
> MesosClusterScheduler reads options from dispatcher conf instead of submission conf
> -----------------------------------------------------------------------------------
>
> Key: SPARK-26192
> URL: https://issues.apache.org/jira/browse/SPARK-26192
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 2.3.0, 2.3.1, 2.3.2, 2.4.0
> Reporter: Martin Loncaric
> Assignee: Martin Loncaric
> Priority: Major
> Fix For: 3.0.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org