[
https://issues.apache.org/jira/browse/MESOS-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014397#comment-14014397
]
Yifan Gu commented on MESOS-1312:
---------------------------------
Hey guys,
I am thinking about working on this issue.
My plan is:
When a slave successfully re-registered with the master, the master will put
those tasks that belongs to some "not-yet-re-registered" framework in an
orphanage, which is basically a hashmap:
hashmap<FrameworkID, hashmap<TaskID, Task*> >
So that users can see those orphan tasks and those not-yet-registered
frameworks via the web-ui.
My concern is that:
If in the future, the frameworks' information is also recorded in the
registrar, at least, two things could be changed. (
1, We will be able to provide more information about the framework besides its
ID.
2, We can show the not-yet-registered frameworks even before the slave
successfully re-registered with the master.
Any suggestion or advice is welcome! Thanks!
> 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)
