[
https://issues.apache.org/jira/browse/SPARK-26192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783810#comment-16783810
]
Martin Loncaric edited comment on SPARK-26192 at 3/4/19 9:51 PM:
-----------------------------------------------------------------
[~dongjoon] Thanks, I will pay more attention to those fields.
However, I believe this is a bug. It violates behavior specified in
https://spark.apache.org/docs/latest/running-on-mesos.html#configuration. Can
we merge into at least 2.4.1 as well?
was (Author: mwlon):
[~dongjoon] Thanks, I will pay more attention to those fields.
However, I believe this is a bug. It violates behavior specified in
https://spark.apache.org/docs/latest/running-on-mesos.html#configuration. Can
we merge into 2.4.1 as well?
> 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: Improvement
> Components: Mesos
> Affects Versions: 2.3.0, 2.3.1, 2.3.2, 2.4.0
> Reporter: Martin Loncaric
> Assignee: Martin Loncaric
> Priority: Minor
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
