[
https://issues.apache.org/jira/browse/TEZ-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897758#comment-15897758
]
Kuhu Shukla commented on TEZ-3628:
----------------------------------
Thank you [~jeagles] for the patch. We can add the change that uses the
provided netty classes for Server Boss Pool( and Worker pool). Once the Netty
versions are updated the code will start using the correct thread name for the
Boss threads. This way we won't need an internal port of {{NioServerBossPool}}.
We can also use simple "+" based string concatenation in
{{determineThreadName}} instead of StringBuilder.
In cases where {{lastIndexOf}} may return -1, the full current name of the
thread is appended to "Tez Shuffle Handler Worker #" which looks OK to me since
the chances of {{lastIndexOf}} not working here are dependent on the Netty
default thread name getting changed in the future releases.
> Give Tez shuffle handler threads custom names
> ---------------------------------------------
>
> Key: TEZ-3628
> URL: https://issues.apache.org/jira/browse/TEZ-3628
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-3628.1.patch
>
>
> Currently, the tez shuffle handler threads are named identically to the map
> reduce shuffle handler threads and can't be distinguished easily.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
