Meng Zhu created MESOS-8624:
-------------------------------
Summary: Agent task launch relies in-order future collect which
`collect()` does not support
Key: MESOS-8624
URL: https://issues.apache.org/jira/browse/MESOS-8624
Project: Mesos
Issue Type: Bug
Affects Versions: 1.5.0
Reporter: Meng Zhu
In https://issues.apache.org/jira/browse/MESOS-1720, agent starts to rely on
in-order task launch between tasks using the same executor, i.e. tasks of the
same executor should be launched in the order the agent receives them.
Otherwise, failures like this (
https://issues.apache.org/jira/browse/MESOS-8617?focusedCommentId=16382531&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16382531)
would occur.
However, the two asynchronous steps (unschedule GC and task authorization) in
the agent task launch path use `collect()` which does not guarantees order
between different collect issued by the same actor. This will result in
out-of-order task launch and cause tasks being dropped or lost:
https://github.com/apache/mesos/blob/32f6d4eec2724414e217875f4f7d3b2538db5381/src/slave/slave.cpp#L2888
One solution is to make collect calls issued by the same actor in order.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)