flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-5718) Handle JVM Fatal Exceptions in Tasks
Date Mon, 06 Feb 2017 11:10:41 GMT
Stephan Ewen created FLINK-5718:
-----------------------------------

             Summary: 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


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)

Mime
View raw message