Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
It would be nice to refactor the code and eliminate some/all of these redundancies:
- Master::activateRecoveredFramework and Master::_failoverFramework duplicate some code.
- Master::_subscribe for PID-based schedulers has a code path that contains code that is very similar to the Master::failoverFramework logic, but is not identical.
- The logic around updateConnection could stand to be cleaned up. e.g., it seems like updateConnection could/should be responsible for linking to the target PID and/or setting up the closed callback (for PID or HTTP schedulers, respectively).
Attachments
Issue Links
- is related to
-
MESOS-6419 The 'master/teardown' endpoint should support tearing down 'unregistered_frameworks'.
- Resolved