You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Renjie Liu (JIRA)" <ji...@apache.org> on 2018/07/24 10:51:00 UTC

[jira] [Created] (FLINK-9936) Mesos resource manager unable to connect to master after failover

Renjie Liu created FLINK-9936:
---------------------------------

             Summary: Mesos resource manager unable to connect to master after failover
                 Key: FLINK-9936
                 URL: https://issues.apache.org/jira/browse/FLINK-9936
             Project: Flink
          Issue Type: Bug
          Components: Mesos, Scheduler
    Affects Versions: 1.5.1, 1.5.0
            Reporter: Renjie Liu
            Assignee: Renjie Liu
             Fix For: 1.6.0


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)