Hi all,

I am trying to run this example on mesos:
https://github.com/jaceklaskowski/spark-activator#master
<https://github.com/jaceklaskowski/spark-activator#master>  

I have mesos 0.21.0 (instead of 0.18.1, could that be a problem?)
I download spark pre built package spark-1.2.0-bin-hadoop2.4.tgz untar it
Create the conf/spark-env.sh file with the following lines:
export MESOS_NATIVE_LIBRARY=/usr/local/lib/libmesos.so
export
SPARK_EXECUTOR_URI=/home/christophe/Development/spark-1.1.1-bin-hadoop2.4.tgz

I create and fill the build.sbt (spark 1.2.0 / scala 2.11.4)
and I am using the src/main/scala/StreamingApp.scala (of the spark
activator) as my main class in Spark

When I submit with .setMaster("local[*]")
The helloer actor is started at
path=akka://sparkDriver/user/Supervisor0/helloer
and it works fine.

But when I submit with .setMaster("mesos://127.0.1.1:5050")
The helloer actor is started at
path=akka://sparkExecutor/user/Supervisor0/helloer
and I get the following log:
Exception in thread "main" akka.actor.ActorNotFound: Actor not found for:
ActorSelection[Anchor(akka://sparkDriver/), Path(/user/Supervisor0/helloer)]

The problem is probably the new path of my actor
It can't be reached by the following url anymore (since its path is
akka://sparkExecutor/user/Supervisor0/helloer) :
val url =
s"akka.tcp://sparkDriver@$driverHost:$driverPort/user/Supervisor0/$actorName"

I have tried many systemActor@host:port but I didn't manage to communicate
with my actor

How can I reach my actor?
Can the mesos 0.21.0 be the source of my problem?
Have I misconfigured anything?
Any ideas?





--
View this message in context: 
http://apache-spark-user-list.1001560.n3.nabble.com/akka-actor-ActorNotFound-In-Spark-Streaming-on-Mesos-using-ssc-actorStream-tp21014.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.

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

Reply via email to