[MESOS-1719] Master should persist framework information

• Type: Task
• Status: Accepted
• Priority: Major
• Resolution: Unresolved
• Component/s: master
• Labels: mesosphere reliability
• Assignee: Unassigned
• Reporter: Vinod Kone
• Shepherd: Benjamin Mahler
• Created: 18/Aug/14 23:55
• Updated: 24/Sep/18 09:30

Description

https://issues.apache.org/jira/browse/MESOS-1219 disallows completed frameworks from re-registering with the same framework id, as long as the master doesn't failover.

This ticket tracks the work for it work across the master failover using registrar.

There are some open questions that need to be addressed:

--> Should registry contain framework ids only framework infos.

For disallowing completed frameworks from re-registering, persisting
framework ids is enough. But, if in the future, we want to disallow
frameworks from re-registering if some parts of framework info
changed then we need to persist the info too.

--> How to update the framework info.
Currently frameworks are allowed to update framework info while re-
registering, but it only takes effect on the master when the master fails
over and on the slave when the slave fails over. How should things
change when persist framework info?

Issue Links

• duplicates: MESOS-3324 Resource leak issue in Mesos
• is blocked by: MESOS-703 master fails to respect updated FrameworkInfo when the framework scheduler restarts
• relates to: MESOS-8160 Support idempotent framework registration
• relates to: MESOS-1219 Master should disallow frameworks that reconnect after failover timeout.
• relates to: MESOS-6232 "Unreachable" metric incremented for non-partition aware tasks during framework failover
• relates to: MESOS-4659 Avoid leaving orphan task after framework failure + master failover
• relates to: MESOS-5761 Improve the logic of orphan tasks
• relates to: MESOS-8636 Master should store `completed` frameworks for lifecycle enforcement separately from that for webUI and endpoints