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

["Till Rohrmann (Jira)" <ji...@apache.org>]

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

Till Rohrmann closed FLINK-6174.
--------------------------------
    Resolution: Abandoned

Issue has been abandoned.

> 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
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)