You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2017/05/19 20:36:04 UTC

[jira] [Commented] (SPARK-20814) Mesos scheduler does not respect spark.executor.extraClassPath configuration

    [ https://issues.apache.org/jira/browse/SPARK-20814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017979#comment-16017979 ] 

Marcelo Vanzin commented on SPARK-20814:
----------------------------------------

Hmm, this sucks, we should fix it for 2.2 (FYI [~marmbrus]).

Let me take a stab at fixing just the Mesos usage without re-introducing that variable.

> Mesos scheduler does not respect spark.executor.extraClassPath configuration
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-20814
>                 URL: https://issues.apache.org/jira/browse/SPARK-20814
>             Project: Spark
>          Issue Type: Bug
>          Components: Mesos
>    Affects Versions: 2.2.0
>            Reporter: Gene Pang
>
> When Spark executors are deployed on Mesos, the Mesos scheduler no longer respects the "spark.executor.extraClassPath" configuration parameter.
> MesosCoarseGrainedSchedulerBackend used to use the environment variable "SPARK_CLASSPATH" to add the value of "spark.executor.extraClassPath" to the executor classpath. However, "SPARK_CLASSPATH" was deprecated, and was removed in this commit [https://github.com/apache/spark/commit/8f0490e22b4c7f1fdf381c70c5894d46b7f7e6fb#diff-387c5d0c916278495fc28420571adf9eL178].
> This effectively broke the ability for users to specify "spark.executor.extraClassPath" for Spark executors deployed on Mesos.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org