Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Duplicate
-
1.0.1
-
None
-
None
-
None
-
centos 7 x64
Description
The problem maybe cause by Mesos and Marathon out of sync
https://github.com/mesosphere/marathon/issues/616
When I found Orphan Tasks happen, I
1. restart marathon
2. marathon do not sync Orphan Tasks, but start new tasks.
3. Orphan Tasks still taked the resource, I have to delete them.
4. I find all Orphan Tasks are under framework `ef169d8a-24fc-41d1-8b0d-c67718937a48-0000`,
curl -XGET `http://c196:5050/master/frameworks` shows that framework is `unregistered_frameworks`
{ "frameworks": [ ..... ], "completed_frameworks": [ ], "unregistered_frameworks": [ "ef169d8a-24fc-41d1-8b0d-c67718937a48-0000", "ef169d8a-24fc-41d1-8b0d-c67718937a48-0000", "ef169d8a-24fc-41d1-8b0d-c67718937a48-0000" ] }
5.Try
curl -XPOST http://c196:5050/master/teardown -d 'frameworkId=ef169d8a-24fc-41d1-8b0d-c67718937a48-0000'
, but get `No framework found with specified ID`
So I have no idea to delete Orphan Tasks
Attachments
Issue Links
- duplicates
-
MESOS-6419 The 'master/teardown' endpoint should support tearing down 'unregistered_frameworks'.
- Resolved
- is related to
-
MESOS-6419 The 'master/teardown' endpoint should support tearing down 'unregistered_frameworks'.
- Resolved