Mesos task ordering guarantees

Hey, I couldn't seem to find any documentation on this.. If a framework responds to an offer with two tasks and they share the same executor (therefore leading to two invocations of *launchTasks()* on the executor), does Mesos provide any guarantees around the order of those tasks being handed to

Re: Mesos task ordering guarantees

Yes. The order is guaranteed. @vinodkone > On Sep 14, 2014, at 5:28 AM, Tom Arnfeld wrote: > > Hey, > > I couldn't seem to find any documentation on this.. > > If a framework responds to an offer with two tasks and they share the same > executor (therefore leading to two invocations of laun

Re: Mesos task ordering guarantees

That's great, thanks Vinod! On Sun, Sep 14, 2014 at 5:33 PM, Vinod Kone wrote: > Yes. The order is guaranteed. > @vinodkone >> On Sep 14, 2014, at 5:28 AM, Tom Arnfeld wrote: >> >> Hey, >> >> I couldn't seem to find any documentation on this.. >> >> If a framework responds to an offer with

Re: Mesos task ordering guarantees

Hey Vinod, On the most part I have indeed observed this to be the case. However every now and then the tasks are being launched out of order. Here's a slave log https://gist.github.com/tarnfeld/7a275e2ddffdc4da9e2f. You can see the slave is assigned the tasks in order, *Task_Tracker_10* first the

Re: Mesos task ordering guarantees

Looked at the code in Slave::runTask() and indeed there is a bug that doesn't guarantee the order of task delivery to an executor. Mind filing a ticket? On Wed, Sep 17, 2014 at 6:22 PM, Tom Arnfeld wrote: > Hey Vinod, > > On the most part I have indeed observed this to be the case. However every

Re: Mesos task ordering guarantees

Thanks for taking a look, created a ticket https://issues.apache.org/jira/browse/MESOS-1812 On 18 September 2014 02:30, Vinod Kone wrote: > Looked at the code in Slave::runTask() and indeed there is a bug that > doesn't guarantee the order of task delivery to an executor. Mind filing a > ticket?