You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/04/19 06:46:00 UTC
[jira] [Reopened] (FLINK-30474) DefaultMultipleComponentLeaderElectionService triggers HA backend change even if it's not the leader
[ https://issues.apache.org/jira/browse/FLINK-30474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Pohl reopened FLINK-30474:
-----------------------------------
> DefaultMultipleComponentLeaderElectionService triggers HA backend change even if it's not the leader
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-30474
> URL: https://issues.apache.org/jira/browse/FLINK-30474
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.16.0, 1.17.0, 1.15.3
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Critical
> Labels: pull-request-available
>
> {{DefaultMultipleComponentLeaderElectionService}} calls {{LeaderElectionEventHandler#onLeaderInformationChange}} in any case even though the contracts of that method states that it should be only called by the leader to update the HA backend information (see [JavaDoc|https://github.com/apache/flink/blob/5a2f220e31c50306a60aae8281f0ab4073fb85e1/flink-runtime/src/main/java/org/apache/flink/runtime/leaderelection/LeaderElectionEventHandler.java#L46-L50]).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)