[
https://issues.apache.org/jira/browse/FLINK-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337158#comment-17337158
]
Ashwin Kolhatkar edited comment on FLINK-11103 at 4/30/21, 7:50 AM:
--------------------------------------------------------------------
Ok, ya that makes sense.
So I'll add the {{Thread.setDefaultUncaughtException}} using utility in the
{{startCluster}} function.
And for {{TaskManagerRunner}} implementations, I can put it in the
{{runTaskManagerProcessSecurely(Configuration configuration)}} function.
That should cover all the entrypoints, right?
was (Author: ashwinkolhatkar):
Ok, ya that makes sense.
So I'll add the {{Thread.setDefaultUncaughtException}} using utility in the
{{startCluster}} function.
And for {{TaskManagerRunner}} implementations, I can put it in the
{{runTaskManagerProcessSecurely(Configurationn configuration)}} function.
That should cover all the entrypoints, right?
> 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)
