[
https://issues.apache.org/jira/browse/FLINK-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994064#comment-15994064
]
ASF GitHub Bot commented on FLINK-5718:
---------------------------------------
Github user zimmermatt commented on the issue:
https://github.com/apache/flink/pull/3811
@tillrohrmann, this is the port of FLINK-5718 to the `release-1.2` branch I
mentioned. It mostly transferred over, but I needed to make some judgement
calls in `TaskManagerConfiguration`, `TaskManagerRuntimeInfo`, and
`JvmExitOnFatalErrorTest`.
Please let me know if you see anything that should be done differently.
> 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)
