You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/08/27 09:38:58 UTC
[jira] [Resolved] (SPARK-2921) Mesos doesn't handle
spark.executor.extraJavaOptions correctly (among other things)
[ https://issues.apache.org/jira/browse/SPARK-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Wendell resolved SPARK-2921.
------------------------------------
Resolution: Duplicate
> Mesos doesn't handle spark.executor.extraJavaOptions correctly (among other things)
> -----------------------------------------------------------------------------------
>
> Key: SPARK-2921
> URL: https://issues.apache.org/jira/browse/SPARK-2921
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 1.0.2
> Reporter: Andrew Or
> Priority: Blocker
> Fix For: 1.1.0
>
>
> The code path to handle this exists only for the coarse grained mode, and even in this mode the java options aren't passed to the executors properly. We currently pass the entire value of spark.executor.extraJavaOptions to the executors as a string without splitting it. We need to use Utils.splitCommandString as in standalone mode.
> I have not confirmed this, but I would assume spark.executor.extraClassPath and spark.executor.extraLibraryPath are also not propagated correctly in either mode.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org