[
https://issues.apache.org/jira/browse/FLINK-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-20047.
---------------------------------
Resolution: Fixed
Fixed via 8bc6a7bae1bc63a44d9d8a5ad2bd629d561dc166
> DefaultLeaderRetrievalService should only notify the LeaderRetrievalListener
> when leader truly changed
> ------------------------------------------------------------------------------------------------------
>
> Key: FLINK-20047
> URL: https://issues.apache.org/jira/browse/FLINK-20047
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> Currently, in {{DefaultLeaderRetrievalService}} we are notifying the
> {{LeaderRetrievalListener}} even though the leader is not truly changed. In
> Kubernetes HA service, we could get lots of leader information notification
> events with same leader. Because the ConfigMap is updated periodically. We
> should filter out these useless events and do not notify the
> {{LeaderRetrievalListener}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
