[
https://issues.apache.org/jira/browse/FLINK-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723547#comment-16723547
]
vinoyang commented on FLINK-11103:
----------------------------------
Oh, I see you mentioned FLINK-5232, and it mainly adds exception catching to
the thread pool of the actor system's dispatcher. So, I thought this is the
same as the issue. However, I think your consideration is reasonable. In
addition to the actor system, TM still uses threads in many places.
> 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)
