Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- is duplicated by
-
MESOS-1719 Master should persist framework information
- Accepted