[jira] [Closed] (SPARK-8675) Executors created by LocalBackend won't get the same classpath as other executor backends

["Andrew Or (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-8675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Or closed SPARK-8675.
----------------------------
          Resolution: Fixed
            Assignee: Min Zhou
       Fix Version/s: 1.5.0
    Target Version/s: 1.5.0

> Executors created by LocalBackend won't get the same classpath as other executor backends 
> ------------------------------------------------------------------------------------------
>
>                 Key: SPARK-8675
>                 URL: https://issues.apache.org/jira/browse/SPARK-8675
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.4.0
>            Reporter: Min Zhou
>            Assignee: Min Zhou
>             Fix For: 1.5.0
>
>
> AFAIK, some spark application always use LocalBackend to do some local initiatives, spark sql is an example.  Starting a LocalPoint won't add user classpath into executor. 
> {noformat}
>   override def start() {
>     localEndpoint = SparkEnv.get.rpcEnv.setupEndpoint(
>       "LocalBackendEndpoint", new LocalEndpoint(SparkEnv.get.rpcEnv, scheduler, this, totalCores))
>   }
> {noformat}
> Thus will cause local executor fail with these scenarios,  loading hadoop built-in native libraries,  loading other user defined native libraries, loading user jars,  reading s3 config from a site.xml file, etc
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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