[
https://issues.apache.org/jira/browse/FLINK-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334716#comment-17334716
]
Till Rohrmann commented on FLINK-11103:
---------------------------------------
I think it would be good if we used the static
{{Thread.setDefaultUncaughtExceptionHandler}} to configure it for all
{{Threads}}. I would suggest to introduce an utility which could be used by all
entrypoints {{ClusterEntrypoint}}, {{YarnTaskExecutorRunner}},
{{KubernetesTaskExecutorRunner}}, {{TaskManagerRunner}}.
For the config key I would suggest to introduce something like
{{cluster.uncaught-exception-handler}} or
{{cluster.uncaught-exception-handling}} and allow it to set it to {{log}} or
{{fail}}.
> Set a default uncaught exception handler
> ----------------------------------------
>
> Key: FLINK-11103
> URL: https://issues.apache.org/jira/browse/FLINK-11103
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.8.0
> Reporter: Nico Kruber
> Assignee: Ashwin Kolhatkar
> Priority: Major
> Labels: stale-major, starter, usability
>
> 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
(v8.3.4#803005)
