Executor initialize before all resources are ready

[Byron Wang <op...@gmail.com>]

Hi, I am building metrics system for Spark Streaming job, in the system, the
metrics are collected in each executor, so a metrics source (a class used to
collect metrics) needs to be initialized in each executor. 
The metrics source is packaged in a jar, when submitting a job, the jar is
sent from local to each executor using the parameter '--jars', however, the
executor starts to initialize the metrics source class before the jar
arrives, as a result, it throws class not found exception.
It seems that if the executor could wait until all resources are ready, the
issue will be resolved, but I really do not know how to do it.

Is there anyone facing the same issue?

PS: I tried using HDFS (copy the jar to HDFS, then submit the job and let
the executor load class from a path in HDFS), but it fails. I checked the
source code, it seems that the class loader can only resolve local path.



--
View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/Executor-initialize-before-all-resources-are-ready-tp25981.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.

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

Re: Executor initialize before all resources are ready

[Ted Yu <yu...@gmail.com>]

Which Spark release are you using ?

Thanks

On Fri, Jan 15, 2016 at 7:08 PM, Byron Wang <op...@gmail.com> wrote:

> Hi, I am building metrics system for Spark Streaming job, in the system,
> the
> metrics are collected in each executor, so a metrics source (a class used
> to
> collect metrics) needs to be initialized in each executor.
> The metrics source is packaged in a jar, when submitting a job, the jar is
> sent from local to each executor using the parameter '--jars', however, the
> executor starts to initialize the metrics source class before the jar
> arrives, as a result, it throws class not found exception.
> It seems that if the executor could wait until all resources are ready, the
> issue will be resolved, but I really do not know how to do it.
>
> Is there anyone facing the same issue?
>
> PS: I tried using HDFS (copy the jar to HDFS, then submit the job and let
> the executor load class from a path in HDFS), but it fails. I checked the
> source code, it seems that the class loader can only resolve local path.
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Executor-initialize-before-all-resources-are-ready-tp25981.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@spark.apache.org
> For additional commands, e-mail: user-help@spark.apache.org
>
>