flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5718) Handle JVM Fatal Exceptions in Tasks
Date Wed, 03 May 2017 15:18:04 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995049#comment-15995049

ASF GitHub Bot commented on FLINK-5718:

Github user tillrohrmann commented on the issue:

    Thanks for your contribution @zimmermatt. Changes look good to me. Merging this PR.

> Handle JVM Fatal Exceptions in Tasks
> ------------------------------------
>                 Key: FLINK-5718
>                 URL: https://issues.apache.org/jira/browse/FLINK-5718
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.3.0
> The TaskManager catches and handles all types of exceptions right now (all {{Throwables}}).
The intention behind that is:
>   - Many {{Error}} subclasses are recoverable for the TaskManagers, such as failure to
load/link user code
>   - We want to give eager notifications to the JobManager in case something in a task
goes wrong.
> However, there are some exceptions which should probably simply terminate the JVM, if
caught in the task thread, because they may leave the JVM in a dysfunctional limbo state:
>   - {{OutOfMemoryError}}
>   - {{InternalError}}
>   - {{UnknownError}}
>   - {{ZipError}}
> These are basically the subclasses of {{VirtualMachineError}}, except for {{StackOverflowError}},
which is recoverable and usually recovered already by the time the exception has been thrown
and the stack unwound.

This message was sent by Atlassian JIRA

View raw message