[FLINK-9936] Mesos resource manager unable to connect to master after failover

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.5.0, 1.5.1, 1.6.0
• Fix Version/s: 1.5.3, 1.6.0
• Component/s: Deployment / Mesos, Runtime / Coordination
• Labels: pull-request-available
• Assignee: Gary Yao
• Reporter: Renjie Liu
• Created: 24/Jul/18 10:50
• Updated: 07/Oct/20 08:56
• Resolved: 03/Aug/18 14:39

Description

When deployed in mesos session cluster mode, the connector monitor keeps reporting unable to connect to mesos after restart. In fact, scheduler driver already connected to mesos master, but when the connected message is lost. This is because leadership is not granted yet and fence id is not set, the rpc service ignores the connected message. So we should connect to mesos master after leadership is granted.

Issue Links

• duplicates: FLINK-7470 Acquire RM leadership before registering with Mesos
• links to: GitHub Pull Request #6451
• links to: GitHub Pull Request #6464