[
https://issues.apache.org/jira/browse/SAMZA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886857#comment-13886857
]
Jakob Homan commented on SAMZA-96:
----------------------------------
What would the configuration be for? My thought had been that in those
instances above, MetricSnapshotReporter and JvmMetrics, each could pass in its
own prefix, ie "MetricsSnapshotReport" or "JvmMetrics". That would make it
easier to identifer their various threads from within the debugger.
> Improve DaemonThreadFactory to specify thread name, use that capability
> -----------------------------------------------------------------------
>
> Key: SAMZA-96
> URL: https://issues.apache.org/jira/browse/SAMZA-96
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Jakob Homan
> Priority: Trivial
> Labels: newbie
> Fix For: 0.7.0
>
>
> The DaemonThreadFactory class is used by the JvmMetrics (line 42) and
> MetricsSnapshotReporter (line 60) classes to create these classes' respective
> threads, but it does not take any way to name the threads that the factory
> creates. When these threads are running and inspected in, say VisualVM,
> they're boringly named Thread-6 or whatever.
> It'd be better to pass the factory a name or naming function and then name
> the metrics threads so they're easier to work with from debuggers.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
