[jira] [Updated] (FLINK-5062) Ensure that all created threads have a proper name

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-5062:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

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


> Ensure that all created threads have a proper name
> --------------------------------------------------
>
>                 Key: FLINK-5062
>                 URL: https://issues.apache.org/jira/browse/FLINK-5062
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task
>    Affects Versions: 1.1.3
>            Reporter: Chesnay Schepler
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> There are a few places where we create a Thread without giving it an explicit name. This can make debugging harder than necessary.
> I've made a sweep some time ago and found the following culprits:
> * ProcessShutDownThread, used in the shutdown of TM/JM
> * StreamPrinter, used by python operators
> * SplitReader, used ContinuousFileReaderOperator
> * CallExecute, used in DataStreamUtils#collect
> In addition we should check for usages of ExecutorServices that don't provide an explicit ThreadFactory (which would allow explicit names).
> I pushed a hotfix today which resolved another occurrence in the MetricRegistry.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)