[
https://issues.apache.org/jira/browse/MESOS-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589950#comment-15589950
]
Gilbert Song commented on MESOS-6400:
-------------------------------------
[~mithril], seems like there are two separate issues from your description:
1. After a network partition or reboot, Marathon should not register with the
Mesos Master using a new FrameworkID, since it would result in the old
frameworkId being regarded as an unregistered_framework and ophan tasks still
occupy the resources which make the new tasks cannot receive enough resources
to launch. (We should contact Marathon team to figure why a new FrameworkID is
used).
2. 'master/teardown' endpoint should support tearing down an unregistered
framework. I created MESOS-6419 to track on this issue.
Side Note:
Currently, the Mesos master does not persist any state of the registered
frameworks, this leads to the master not able to figure out when a new
framework id try to register whether or not it exists before. Ideally, the
Mesos master should persist all framework information on disk (as it currently
does with the agent information). There should be an early JIRA describing this
issue. Will link it once I find it.
> 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
>
> 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)
