[
https://issues.apache.org/jira/browse/FLINK-29173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682029#comment-17682029
]
Matthias Pohl commented on FLINK-29173:
---------------------------------------
I'm inclined to close this issue:
* FLINK-30772 will update curator for 1.17 and, therefore, is a (partial)
duplicate of this issue.
* 1.15 is not gonna be supported after 1.17 is out.
* We fixed FLINK-28078 through a workaround and FLINK-30484 doesn't come up
that often (and if so, we could use the very same workaround from FLINK-28078
to fix it).
That way, we avoid doing another flink-shaded 16.2 release.
> Upgrade curator
> ---------------
>
> Key: FLINK-29173
> URL: https://issues.apache.org/jira/browse/FLINK-29173
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.16.0, 1.17.0, 1.15.3
> Reporter: Matthias Pohl
> Priority: Major
>
> FLINK-28078 revealed a bug in curator's LeaderLatch implementation that is
> covered by CURATOR-645. FLINK-28078 came up with a workaround in
> {{ZooKeeperMultipleComponentLeaderElectionDriverTest.testLeaderElectionWithMultipleDrivers}}
> (see
> [655184c|https://github.com/apache/flink/commit/655184cdb086ac2adec3e743701868f1a55b6129]
> {{master}} and
> [ed8700d|https://github.com/apache/flink/commit/ed8700d03cccc47bfa39da5e1e6611eb9be7d5a1]
> for {{release-1.15}}) that should get reverted after the curator version was
> bumbed to a version that includes CURATOR-645.
> There's a similar issue CURATOR-644 which we didn't run into but we might
> want to observe and include as well, probably.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
