You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/02/02 14:42:00 UTC

[jira] [Updated] (FLINK-23843) Exceptions during "SplitEnumeratorContext.runInCoordinatorThread()" should cause Global Failure instead of Process Kill

     [ https://issues.apache.org/jira/browse/FLINK-23843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-23843:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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: Etienne Chauchot
>            Priority: Critical
>              Labels: pull-request-available
>             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)