[ https://issues.apache.org/jira/browse/FLINK-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330471#comment-17330471 ]
Nico Kruber commented on FLINK-11103: ------------------------------------- [~trohrmann], I think the previous ping may not have reached you. I think, this should be a fairly simple change that helps us a lot with debugging applications that may have rogue threads and behave strangely even though, no error appears in the logs. > 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 > 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)