[
https://issues.apache.org/jira/browse/FLINK-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723157#comment-16723157
]
Nico Kruber edited comment on FLINK-11103 at 12/17/18 4:54 PM:
---------------------------------------------------------------
Maybe I did not look into FLINK-5232 thoroughly enough: I wasn't referring to
any akka actor system, but instead any thread in Flink including those which
can be spawned by users. Do you think, your commit also covers this?
was (Author: nicok):
Maybe I did not look into FLINK-5232 thoroughly enough: I wasn't referring to
any akka actor system, but instead any thread in Flink including those which
can be spawned by users.
> Set a default uncaught exception handler
> ----------------------------------------
>
> Key: FLINK-11103
> URL: https://issues.apache.org/jira/browse/FLINK-11103
> Project: Flink
> Issue Type: Improvement
> Components: TaskManager
> Affects Versions: 1.8.0
> Reporter: Nico Kruber
> Assignee: vinoyang
> Priority: Major
>
> We should set a default uncaught exception handler in Flink via
> {{Thread.setDefaultUncaughtExceptionHandler()}} which at least logs the
> exceptions. Ideally, we would even fail the job (could make this
> configurable) but users may have some ill-behaving threads, e.g. through
> libraries, which they would want to tolerate and we don't want to change
> behaviour now.
> (FLINK-5232 added this for the JobManager, we need it for the TaskManager)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
