Its not the port for the mesos slave that I want to set, there is another port used for communicating between the mesos master and the spark tasks, here are some example log lines.
In this case if the port 56311 is not opened up via iptables and security groups, the detecting new master step will hang indefinitely The log lines are coming from the mesos native lib, so not sure if spark can pass in a port here rather than defaulting to 0 / random. group.cpp:310] Group process ((2)@1.2.3.4:56311) connected to ZooKeeper group.cpp:752] Syncing group operations: queue size (joins, cancels, datas) = (0, 0, 0) group.cpp:367] Trying to create path '/mesos' in ZooKeeper detector.cpp:134] Detected a new leader: (id='2') group.cpp:629] Trying to get '/mesos/info_0000000002' in ZooKeeper detector.cpp:351] A new leading master (UPID=master@10.118.41.27:5050) is detected sched.cpp:230] Detecting new master -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/spark-mesos-configure-mesos-callback-port-tp5475p5675.html Sent from the Apache Spark User List mailing list archive at Nabble.com.
