Hi Alex, I think I talked to you on IRC the other day. Thanks for responding. Yes, the problem was the implicitAknowledge default is backwards in the python bindings I have. I still think (but haven't yet verified) that I have some weird conflicting python egg. I'll reinstall from scratch at some point and make sure I have all the correct things.
Thanks so much for your help! Zack On Wed, Apr 22, 2015 at 2:42 AM, Alexander Rojas <[email protected]> wrote: > Hey Zack, > > Which value are you for the setting implicitAknowledge parameter in the > SchedulerDriver constructor? if it is set to false, you will have to > manually knowledge every statusUpdate, otherwise the executor will try to > retry. > > Are you using the python bindings? It seems that the default value there > is set to false. > > Alexander > > > > On 20 Apr 2015, at 16:25, Zack Booth Simpson <[email protected]> > wrote: > > > > I'm building a simple framework as a proof of concept. I launchTasks() > > successfully and my job (which is nothing but a sleep and an echo) runs > > fine. I can see its output in the trace files. Mesos UI says "FINSIHED" > but > > statusUpdate keeps returning RUNNING to me over and over again. > > > > Any ideas? > > > > Zack > >
