[
https://issues.apache.org/jira/browse/FLINK-23843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17473207#comment-17473207
]
Steven Zhen Wu commented on FLINK-23843:
----------------------------------------
I am not sure what's the right way to fix it. But Stephan's original
description makes sense to me. We don't want exception to cause kill of
jobmanager process. Rather a full job restart is expected in this case.
> Exceptions during "SplitEnumeratorContext.runInCoordinatorThread()" should
> cause Global Failure instead of Process Kill
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-23843
> URL: https://issues.apache.org/jira/browse/FLINK-23843
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.13.2
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Critical
> Fix For: 1.15.0
>
>
> Currently, when a the method
> "SplitEnumeratorContext.runInCoordinatorThread()" throws an exception, the
> effect is a process kill of the JobManager process.
> The chain how the process kill happens is:
> * An exception bubbling up in the executor, killing the executor thread
> * The executor starts a replacement thread, which is forbidden by the thread
> factory (as a safety net) and causes a process kill.
> We should prevent such exceptions from bubbling up in the coordinator
> executor.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
