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.

Reply via email to