You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2014/05/05 16:25:14 UTC

[jira] [Commented] (SPARK-1680) Clean up use of setExecutorEnvs in SparkConf

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

Thomas Graves commented on SPARK-1680:
--------------------------------------

I think this is dup of SPARK-1665.

> Clean up use of setExecutorEnvs in SparkConf 
> ---------------------------------------------
>
>                 Key: SPARK-1680
>                 URL: https://issues.apache.org/jira/browse/SPARK-1680
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Spark Core
>    Affects Versions: 1.0.0
>            Reporter: Patrick Wendell
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> This was added in 0.9.0 but the config change removed propagation of these values to executors. We should make one of two decisions:
> 1. Don't allow setting arbitrary executor envs in standalone mode.
> 2. Document this option, respect the env variables when launching a job, and consolidate this with SPARK_YARN_USER_ENV.



--
This message was sent by Atlassian JIRA
(v6.2#6252)