[
https://issues.apache.org/jira/browse/MESOS-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014444#comment-14014444
]
Yifan Gu commented on MESOS-1312:
---------------------------------
Thanks Vinod,
That's right, So by now, the WebUI renders the tasks information by iterating
over the frameworks.
So I guess we can add those "orphan" tasks to the tasks.json. And we can render
all tasks by looking at the tasks.json, (Ross told me that the tasks.json is a
new feature after the WebUI).
But that will have the javascript part to do some work to tell whether a task
is active, completed or "orphaned".
Especially its a little bit tricky to tell if a task is "orphaned". (Or we can
just think it is active, which is also true).
What's your opinion on that?
> Show active tasks orphaned by a framework disconnect
> ----------------------------------------------------
>
> Key: MESOS-1312
> URL: https://issues.apache.org/jira/browse/MESOS-1312
> Project: Mesos
> Issue Type: Improvement
> Components: webui
> Affects Versions: 0.18.0, 0.19.0
> Reporter: Burke Libbey
> Priority: Minor
>
> When I fail over from one mesos-master to another, I have a framework that
> doesn't reregister to the new master. This causes its previously-spawned
> tasks to not appear in the front page of the mesos-master webui.
> It would be nice to have an "orphaned tasks" section or something, as
> mentioned in the IRC logs:
> http://wilderness.apache.org/channels/?f=mesos/2014-05-06#1399406277
--
This message was sent by Atlassian JIRA
(v6.2#6252)
