You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2022/06/02 03:01:00 UTC
[jira] [Closed] (FLINK-27848) ZooKeeperLeaderElectionDriver keeps writing leader information, using up zxid
[ https://issues.apache.org/jira/browse/FLINK-27848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xintong Song closed FLINK-27848.
--------------------------------
Resolution: Fixed
Fixed in:
- release-1.15: 73a33ab5f25dd5ac7e8adb1521c092a8aedcc736
> ZooKeeperLeaderElectionDriver keeps writing leader information, using up zxid
> -----------------------------------------------------------------------------
>
> Key: FLINK-27848
> URL: https://issues.apache.org/jira/browse/FLINK-27848
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.15.0
> Reporter: Xintong Song
> Assignee: Weijie Guo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.1
>
>
> After a leadership change, the new leader may keeps writing its information (which is identical) to ZK, causing the zxid on ZK quickly used up.
> The problem is that, in {{ZooKeeperLeaderElectionDriver#retrieveLeaderInformationFromZooKeeper}}, {{leaderElectionEventHandler.onLeaderInformationChange(LeaderInformation.empty())}} is called no matter {{childData}} is {{null}} or not. In case of non-null, this will cause the driver keeps re-writing the leader information to ZK.
> The problem was introduced in FLINK-24038, and only affects the legacy {{ZooKeeperHaServices}}. Thus, only 1.15 are affected.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)