[MESOS-6419] The 'master/teardown' endpoint should support tearing down 'unregistered_frameworks'.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.26.2, 0.27.3, 0.28.2, 1.0.1
• Fix Version/s: 1.2.0
• Component/s: master
• Labels: endpoint master
• Target Version/s: 1.2.0
• Sprint: Mesosphere Sprint 48, Mesosphere Sprint 49
• Story Points: 8
• Assignee: Neil Conway
• Reporter: Gilbert Song
• Shepherd: Vinod Kone
• Created: 19/Oct/16 19:41
• Updated: 23/Jan/17 20:45
• Resolved: 17/Jan/17 08:23

Description

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

Issue Links

• is duplicated by: MESOS-6400 Not able to remove Orphan Tasks
• is related to: MESOS-4659 Avoid leaving orphan task after framework failure + master failover
• is related to: MESOS-6586 Teardown endpoint should remove framework
• is required by: MESOS-6719 Unify "active" and "state"/"connected" fields in Master::Framework
• relates to: MESOS-6753 Refactor duplicated code for framework registration in master
• relates to: MESOS-6400 Not able to remove Orphan Tasks
• requires: MESOS-6675 Change allocator API to support adding inactive frameworks