[FLINK-7470] Acquire RM leadership before registering with Mesos

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: Deployment / Mesos
• Assignee: Unassigned
• Reporter: Eron Wright
• Created: 17/Aug/17 20:10
• Updated: 21/Nov/18 16:52
• Resolved: 21/Nov/18 16:52

Description

Mesos doesn't support fencing tokens in the scheduler protocol; it assumes external leader election among scheduler instances. The last connection wins; prior connections for a given framework ID are closed.

The Mesos RM should not register as a framework until it has acquired RM leadership. Evolve the ResourceManager as necessary. One option is to introduce an ResourceManagerRunner that acquires leadership before starting the RM.

Issue Links

• is duplicated by: FLINK-9936 Mesos resource manager unable to connect to master after failover