Hi David, Is your discovery service part of the Executor ? Some more context of the interaction of the Executor and the discovery service would be helpful. If the discovery service is relying specifically on multicast, and you no the packet payload for the discovery messages, might help to run tcpdump on the NIC to see if the messages are going out when you start your executor.
Thanks, Avinash On Tue, Mar 1, 2016 at 1:40 PM, David Wood <[email protected]> wrote: > I'm building an Executor that uses a separate discovery service that > relies on multicast. If I run the executor without calling > MesosExecutorDriver.run() the executor discovers other (non-mesos) nodes in > my distributed set up just fine. But if I call run(), then it does not > discover the other nodes. Interestingly, the other nodes can discover my > executor regardless of whether run() is called or not. My executor is a > Java app started using a command line task. Any help is much appreciated. > > > David Wood > Computing Systems for Wireless Networks > IBM TJ Watson Research Center > [email protected] > 914-945-4923 (office), 914-396-6515 (mobile) > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245
