[ 
https://issues.apache.org/jira/browse/MESOS-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725065#comment-14725065
 ] 

Yong Qiao Wang commented on MESOS-3324:
---------------------------------------

Thanks [~bmahler], if there is no other existing ticket to trace this issue, 
can we update the title of this ticket to "Enhancement to persist framework 
information in the registry"? And I will try to fix this issue later. I request 
you as a shepherd of me, and will have a discussion and give me some 
suggestions of this issue later. Thanks in advance.

> Resource leak issue in Mesos
> ----------------------------
>
>                 Key: MESOS-3324
>                 URL: https://issues.apache.org/jira/browse/MESOS-3324
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Yong Qiao Wang
>            Assignee: Yong Qiao Wang
>            Priority: Critical
>
> In Mesos master recovery case, if one framework is exit during Mesos master 
> downtime and this framework has already launched some long running tasks 
> before Mesos master down. Then after Mesos master recovery, those long 
> running tasks will always running as the orphaned tasks in Mesos cluster, no 
> any other components can kill those tasks later. This should be a resource 
> leak issue in Mesos, I propose to add a timeout to kill those orphaned tasks 
> or executors in Mesos master.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to