[
https://issues.apache.org/jira/browse/MESOS-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613513#comment-15613513
]
Gilbert Song commented on MESOS-6400:
-------------------------------------
[~mithril], thanks for recording the logs. We will address all related tech
debt in Mesos. BTW, you can resolve the orphan task issue by tearing down the
unregistered marathon framework using the workaround in the following doc:
https://gist.github.com/bernadinm/41bca6058f9137cd21f4fb562fd20d50
> Not able to remove Orphan Tasks
> -------------------------------
>
> Key: MESOS-6400
> URL: https://issues.apache.org/jira/browse/MESOS-6400
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.0.1
> Environment: centos 7 x64
> Reporter: kasim
> Priority: Critical
>
> 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`
> {code}
> {
> "frameworks": [
> .....
> ],
> "completed_frameworks": [ ],
> "unregistered_frameworks": [
> "ef169d8a-24fc-41d1-8b0d-c67718937a48-0000",
> "ef169d8a-24fc-41d1-8b0d-c67718937a48-0000",
> "ef169d8a-24fc-41d1-8b0d-c67718937a48-0000"
> ]
> }
> {code}
> 5.Try {code}curl -XPOST http://c196:5050/master/teardown -d
> 'frameworkId=ef169d8a-24fc-41d1-8b0d-c67718937a48-0000' {code}
> ， but get `No framework found with specified ID`
> So I have no idea to delete Orphan Tasks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
