Chesnay Schepler created FLINK-5062:
---------------------------------------
Summary: Ensure that all create threads have a proper name
Key: FLINK-5062
URL: https://issues.apache.org/jira/browse/FLINK-5062
Project: Flink
Issue Type: Improvement
Affects Versions: 1.1.3
Reporter: Chesnay Schepler
Fix For: 1.2.0
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
(v6.3.4#6332)
