[
https://issues.apache.org/jira/browse/FLINK-32678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747317#comment-17747317
]
Matthias Pohl commented on FLINK-32678:
---------------------------------------
[~wangyang0918] I'm wondering whether we could use this test as an umbrella
test for two other topics that ended up in the 1.18 release:
* FLINK-32032 (flink-shaded update including netty)
* FLINK-32468 (Migration from Akka to Pekko)
They are quite fundamental changes and hard to test in a manual way. The
proposal would be to do a stress test on Flink 1.18. For FLINK-32032 and
FLINK-32468, observing that nothing breaks might be good enough. WDYT?
> Test FLIP-285 LeaderElection
> ----------------------------
>
> Key: FLINK-32678
> URL: https://issues.apache.org/jira/browse/FLINK-32678
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Affects Versions: 1.18.0
> Reporter: Matthias Pohl
> Assignee: Yang Wang
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.18.0
>
>
> We decided to do another round of testing for the LeaderElection refactoring
> which happened in
> [FLIP-285|https://cwiki.apache.org/confluence/display/FLINK/FLIP-285%3A+refactoring+leaderelection+to+make+flink+support+multi-component+leader+election+out-of-the-box].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
