You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gastón Kleiman (JIRA)" <ji...@apache.org> on 2017/11/01 20:59:12 UTC
[jira] [Comment Edited] (MESOS-8135) Masters can lose track of
executor IDs.
[ https://issues.apache.org/jira/browse/MESOS-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221882#comment-16221882 ]
Gastón Kleiman edited comment on MESOS-8135 at 11/1/17 8:58 PM:
----------------------------------------------------------------
https://reviews.apache.org/r/63353/
https://reviews.apache.org/r/63474/
was (Author: gkleiman):
https://reviews.apache.org/r/63353/
> Masters can lose track of executor IDs.
> ---------------------------------------
>
> Key: MESOS-8135
> URL: https://issues.apache.org/jira/browse/MESOS-8135
> Project: Mesos
> Issue Type: Bug
> Components: agent
> Reporter: Gastón Kleiman
> Assignee: Gastón Kleiman
> Priority: Major
> Labels: mesosphere, mesosphere-oncall
>
> The response to the master's {{state}} endpoint sometimes doesn't include the executor id corresponding to some tasks.
> Agents send to the leading master a list of tasks when reregistering. Tasks that are not started by the command executor should contain an executor id, but the following snippet can sometimes clear the executor id of tasks started by other executors: https://github.com/apache/mesos/blob/1.4.0/src/slave/slave.cpp#L1515-L1522
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)