[
https://issues.apache.org/jira/browse/MESOS-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824796#comment-15824796
]
Adam B commented on MESOS-6419:
-------------------------------
[~neilc], [~vinodkone] I removed the 1.1.1 TargetVersion, since I doubt we'll
backport this much code.
Since all those patches have already landed in master, is there anything else
we need to do for Mesos 1.2? If not, let's resolve this ticket.
> The 'master/teardown' endpoint should support tearing down
> 'unregistered_frameworks'.
> -------------------------------------------------------------------------------------
>
> Key: MESOS-6419
> URL: https://issues.apache.org/jira/browse/MESOS-6419
> Project: Mesos
> Issue Type: Bug
> Components: master
> Affects Versions: 0.26.2, 0.27.3, 0.28.2, 1.0.1
> Reporter: Gilbert Song
> Assignee: Neil Conway
> Priority: Critical
> Labels: endpoint, master
> Fix For: 1.2.0
>
>
> This issue is exposed from
> [MESOS-6400](https://issues.apache.org/jira/browse/MESOS-6400). When a user
> is trying to tear down an 'unregistered_framework' from the 'master/teardown'
> endpoint, a bad request will be returned: `No framework found with specified
> ID`.
> Ideally, we should support tearing down an unregistered framework, since
> those frameworks may occur due to network partition, then all the orphan
> tasks still occupy the resources. It would be a nightmare if a user has to
> wait until the unregistered framework to get those resources back.
> This may be the initial implementation:
> https://github.com/apache/mesos/commit/bb8375975e92ee722befb478ddc3b2541d1ccaa9
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
