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 then *slots_Task_Tracker_10* which is the order they should be. Though they are queued for launching by the executor in the wrong order. On 14 September 2014 19:46, Tom Arnfeld <[email protected]> wrote: > That's great, thanks Vinod! > > > On Sun, Sep 14, 2014 at 5:33 PM, Vinod Kone <[email protected]> wrote: > >> Yes. The order is guaranteed. >> >> @vinodkone >> >> On Sep 14, 2014, at 5:28 AM, Tom Arnfeld <[email protected]> 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 *launchTasks()* on >> the executor), does Mesos provide any guarantees around the order of those >> tasks being handed to the executor once it comes up? >> >> Given that the LaunchTasksMessage protobuf contains a repeated TaskInfo tasks >> does this mean the order will be honoured? >> >> Thanks, >> >> Tom. >> >> >
