You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/05 10:55:03 UTC

[jira] [Updated] (FLINK-11103) Set a default uncaught exception handler

     [ https://issues.apache.org/jira/browse/FLINK-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-11103:
-----------------------------------
      Labels: auto-deprioritized-major pull-request-available starter usability  (was: pull-request-available stale-major starter usability)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> 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.13.0
>            Reporter: Nico Kruber
>            Assignee: Ashwin Kolhatkar
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, 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)