[
https://issues.apache.org/jira/browse/FLINK-32029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721280#comment-17721280
]
Matthias Pohl edited comment on FLINK-32029 at 5/10/23 4:15 PM:
----------------------------------------------------------------
master: 88b3432a2845952543a8396aeb8e2cddab77b509
1.17: 1d85f6ffc00789e0239f8ed7164af03b81e8dfae
1.16: 55c748647fdf68050312c08bfaba574a423a8464
was (Author: mapohl):
master: 88b3432a2845952543a8396aeb8e2cddab77b509
1.17: tba
1.16: tba
> FutureUtils.handleUncaughtException swallows exceptions that are caused by
> the exception handler code
> -----------------------------------------------------------------------------------------------------
>
> Key: FLINK-32029
> URL: https://issues.apache.org/jira/browse/FLINK-32029
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.17.0, 1.16.1, 1.18.0
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Major
> Labels: pull-request-available
>
> I ran into an issue in FLINK-31773 where the passed exception handler relies
> on the {{leaderContender}} field of the {{DefaultLeaderElectionService}}.
> This field can become {{null}} with the changes of FLINK-31773. But the
> {{null}} check was missed in the error handling code. This bug wasn't exposed
> because {{FutureUtils.handleUncaughtException(..)}} expects the passed error
> handler callback to be bug-free.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
