[
https://issues.apache.org/jira/browse/FLINK-18677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-18677.
---------------------------------
Fix Version/s: 1.11.2
1.10.2
Resolution: Fixed
Fixed via
master: cf8b882af788d467f43643d22d82a6a221860e24
1.11.2: 1c66bfa74dc88ea1b0733c529715dc434003e867
1.10.2: d954278bb1dc1672fedcd2de745bfe8f5bad6e34
> 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.10.1, 1.12.0, 1.11.1
> Reporter: Till Rohrmann
> Assignee: Matthias
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.2, 1.12.0, 1.11.2
>
>
> 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)
