[
https://issues.apache.org/jira/browse/FLINK-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937694#comment-15937694
]
ASF GitHub Bot commented on FLINK-6174:
---------------------------------------
Github user wenlong88 commented on the issue:
https://github.com/apache/flink/pull/3599
Hi, @WangTaoTheTonic I think we can improve the reaction of
ZookeeperLeaderElectionService on zookeeper connection expired or other errors
instead of introducing the AlwaysLeaderService such as adding a retry before
revoking leadership, because when the problem is caused by errors on the
machine which JM is running on, we need to trigger a failover to make the JM
change a machine.
On the other hand, in the coming FLIP-6 implementation, JM failover will
not trigger cancelling all running tasks.
> 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: Improvement
> Components: JobManager
> Reporter: Tao Wang
> Assignee: Tao Wang
>
> 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
(v6.3.15#6346)
