[
https://issues.apache.org/jira/browse/MESOS-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637337#comment-15637337
]
Yan Xu commented on MESOS-6550:
-------------------------------
There are two issues:
1. Duplicate entries.
2. Tasks being transitioned to completed but with a RUNNING state.
The first issue actually also happens with a PARTITION_AWARE framework, in
which case the task is transitioned from TASK_UNREACHABLE -> TASK_RUNNING after
the unreachable agent comes back but the stale entry is still in the "completed
tasks" section. Perhaps this condition is worth a JIRA of its own?
> Mesos master ui shows a Lost task as Running in Completed tasks section
> -----------------------------------------------------------------------
>
> Key: MESOS-6550
> URL: https://issues.apache.org/jira/browse/MESOS-6550
> Project: Mesos
> Issue Type: Bug
> Components: slave
> Reporter: Megha
> Attachments: screenshot-1.png
>
>
> This is particularly happening when an agent is marked unreachable and as a
> result master marks the tasks from partition unaware frameworks as lost but
> when the agent comes back up then we see another instance of this task (from
> unaware framework) as running on the master ui in the completed tasks section
> although the master already sent a task kill for this task and agent acted on
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
