Hi @vinodkone nimbus log: 2014-08-18 15:49:53 b.s.d.nimbus [INFO] Executor wordcount-1-1408376868:[2 2] not alive 2014-08-18 15:49:53 b.s.d.nimbus [INFO] Executor wordcount-1-1408376868:[2 2] not alive 2014-08-18 15:49:53 b.s.d.nimbus [INFO] Executor wordcount-1-1408376868:[3 3] not alive 2014-08-18 15:49:53 b.s.d.nimbus [INFO] Executor wordcount-1-1408376868:[3 3] not alive
for all the executors. On the mesos slave, there are no storm related logs. Which leads me to believe that there's no supervisor to be found, even-though there's obviously an executor that's assigned to the job. My understanding is that Mesos is responsible for spawning the supervisors (although that's not explicitly stated anywhere). The documentation is not very clear. But if I run the supervisors, then Mesos can't do the resource allocation as it's supposed to. (Y) On Aug 18, 2014, at 6:13 PM, Vinod Kone <vinodk...@gmail.com> wrote: > Can you paste the slave/executor log related to the executor failure? > > @vinodkone > > On Aug 18, 2014, at 5:05 AM, Yaron Rosenbaum <ya...@whatson-social.com> wrote: > >> Hi >> >> I have created a Docker based Mesos setup, including chronos, marathon, and >> storm. >> Following advice I saw previously on this mailing list, I have run all >> frameworks directly on the Mesos master (is this correct? is it guaranteed >> to have only one master at any given time?) >> >> Chronos and marathon work perfectly, but storm doesn't. UI works, but it >> seems like supervisors are not able to communicate with nimbus. I can deploy >> topologies, but the executors fail. >> >> Here's the project on github: >> https://github.com/yaronr/docker-mesos >> >> I've spent over a week on this and I'm hitting a wall. >> >> >> Thanks! >> >> (Y) >>
