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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/27 10:08:00 UTC

[jira] [Updated] (FLINK-6174) Introduce a leader election service in yarn mode to make JobManager always available

     [ https://issues.apache.org/jira/browse/FLINK-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-6174:
----------------------------------
    Labels: pull-request-available  (was: )

> Introduce a leader election service in yarn mode to make JobManager always available
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-6174
>                 URL: https://issues.apache.org/jira/browse/FLINK-6174
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Tao Wang
>            Assignee: Tao Wang
>            Priority: Major
>              Labels: pull-request-available
>
> Now in yarn mode, if we use zookeeper as high availability choice, it will create a election service to get a leader depending on zookeeper election.
> When zookeeper leader crashes or the connection between JobManager and zookeeper instance was broken, JobManager's leadership will be revoked and send a Disconnect message to TaskManager, which will cancle all running tasks and make them waiting connection rebuild between JM and ZK.
> In yarn mode, we have one and only JobManager(AM) in same time, and it should be alwasy leader instead of elected through zookeeper. We can introduce a new leader election service in yarn mode to achive that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)