[
https://issues.apache.org/jira/browse/MESOS-8824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Xu reassigned MESOS-8824:
-----------------------------
Assignee: Yan Xu
> Send the task's latest "status update state" to frameworks when an
> unreachable agent reregisters.
> -------------------------------------------------------------------------------------------------
>
> Key: MESOS-8824
> URL: https://issues.apache.org/jira/browse/MESOS-8824
> Project: Mesos
> Issue Type: Bug
> Reporter: Yan Xu
> Assignee: Yan Xu
> Priority: Major
>
> With MESOS-6406 the master started to actively send frameworks status updates
> for reregistering agents if the agent:
> - has previously been removed by the master for being unreachable or
> - is unknown to the master due to the garbage collection of the
> unreachable and gone agents in the registry and the master's state.
> However we sent the task's [latest
> state|https://github.com/apache/mesos/blob/3711d66aa9eb70e12b184d3c2f79bf56fbd9cffa/include/mesos/v1/mesos.proto#L2147]
> instead of its [latest status update
> state|https://github.com/apache/mesos/blob/3711d66aa9eb70e12b184d3c2f79bf56fbd9cffa/include/mesos/v1/mesos.proto#L2154]
> which means the framework could first get an update with a {{TASK_FINISHED}}
> and then later {{TASK_RUNNING}}.
> This is inconsistent with the handling of other master generated updates,
> e.g,. [during
> reconciliation|https://github.com/apache/mesos/blob/3711d66aa9eb70e12b184d3c2f79bf56fbd9cffa/src/master/master.cpp#L8603];
> we should send the status update state instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
