Hm, I've seen the issue with Bridge networking where the IP advertised by libprocess in the container is not reachable by the master, i.e. https://issues.apache.org/jira/browse/MESOS-2587. I've see this ticket is resolved, however. It may require a patch in Spark itself. If possible, you could try with host networking and see if the issue still exists.
-Elizabeth On Thu, Oct 22, 2015 at 12:08 PM, Stavros Kontopoulos < [email protected]> wrote: > Bridge... with the latest mesos library vesion 0.25... > > On Thu, Oct 22, 2015 at 9:07 PM, Elizabeth Lingg <[email protected]> > wrote: > >> Are you using Bridge or Host Networking? >> >> -Elizabeth >> >> >> >> On Thu, Oct 22, 2015 at 12:02 PM, Stavros Kontopoulos < >> [email protected]> wrote: >> >>> Hi, >>> >>> Im using spark on mesos on docker. I have linked my slaves to the master >>> and a >>> spark repl works fine inside the master container. >>> >>> If i try to crate the same spark repl form the host i get stuck at the >>> point when the framework tries to register to the mesos master (here the >>> framework is the spark repl itself). >>> I can ping the container from my host and vice versa. So networking its >>> not the problem. >>> What i noticed form the logs is that mesos does not resolve the correct >>> ip: >>> >>> Framework failover timeout, removing framework >>> b3605c33-f573-4d40-806f-b9b0abee2e32-0012 (Spark shell) at >>> [email protected]:40186 >>> >>> docker0 interface is on 172.17.x.x and my host is one such ip so i didnt >>> expect there to see >>> 127.0.1.1. I have tried several things like spark.driver.host, >>> SPARK_LOCAL_IP to be set correctly but with no result... >>> I suspect this is a mesos problem on docker... >>> >>> Thnx, >>> >>> S. >>> >> >> >
