You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/07/22 21:17:00 UTC
[jira] [Created] (FLINK-18677) ZooKeeperLeaderRetrievalService does
not invalidate leader in case of SUSPENDED connection
Till Rohrmann created FLINK-18677:
-------------------------------------
Summary: ZooKeeperLeaderRetrievalService does not invalidate leader in case of SUSPENDED connection
Key: FLINK-18677
URL: https://issues.apache.org/jira/browse/FLINK-18677
Project: Flink
Issue Type: Bug
Components: Runtime / Coordination
Affects Versions: 1.11.1, 1.10.1, 1.12.0
Reporter: Till Rohrmann
Fix For: 1.12.0
The {{ZooKeeperLeaderRetrievalService}} does not invalidate the leader if the ZooKeeper connection gets SUSPENDED. This means that a {{TaskManager}} won't cancel its running tasks even though it might miss a leader change. I think we should at least make it configurable whether in such a situation the leader listener should be informed about the lost leadership. Otherwise, we might run into the situation where an old and a newly recovered instance of a {{Task}} can run at the same time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)