Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
1.5.0, 1.5.1, 1.6.0
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.
Attachments
Issue Links
- duplicates
-
FLINK-7470 Acquire RM leadership before registering with Mesos
- Closed
- links to