[
https://issues.apache.org/jira/browse/FLINK-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336836#comment-17336836
]
Flink Jira Bot commented on FLINK-5062:
---------------------------------------
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.
> 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: Major
> Labels: stale-major
>
> 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.3.4#803005)
