[
https://issues.apache.org/jira/browse/FLINK-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998385#comment-15998385
]
ASF GitHub Bot commented on FLINK-5718:
---------------------------------------
GitHub user zimmermatt reopened a pull request:
https://github.com/apache/flink/pull/3811
[FLINK-5718] [core] TaskManagers exit the JVM on fatal exceptions.
Manually applied and adapted commit
dfc6fba5b9830e6a7804a6a0c9f69b36bf772730 for
the `release-1.2` branch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zimmermatt/flink release-1.2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3811.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3811
----
commit d50acea7ab7d53454de761a4391159ab81dbd63c
Author: Matt Zimmer <zimmerm...@netflix.com>
Date: 2017-05-02T23:46:13Z
[FLINK-5718] [core] TaskManagers exit the JVM on fatal exceptions.
Manually applied and adapted commit
dfc6fba5b9830e6a7804a6a0c9f69b36bf772730 for
the `release-1.2` branch.
commit fb3d99002e289b667e7a1533277e90d6186751e8
Author: Matt Zimmer <zimmerm...@netflix.com>
Date: 2017-05-03T18:04:17Z
Merge remote-tracking branch 'upstream/release-1.2' into release-1.2
----
> 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
(v6.3.15#6346)
