You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Yong Qiao Wang (JIRA)" <ji...@apache.org> on 2015/08/27 10:21:45 UTC

[jira] [Updated] (MESOS-3324) Resource leak issue in Mesos

     [ https://issues.apache.org/jira/browse/MESOS-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yong Qiao Wang updated MESOS-3324:
----------------------------------
    Summary: Resource leak issue in Mesos  (was: Resource leak issue)

> 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)