[
https://issues.apache.org/jira/browse/HDFS-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Vadali updated HDFS-1055:
----------------------------------
Attachment: dataxceiver-merged.patch
Merged Todd Lipcon's changes.
In trunk DataXceiver extends DataTransferProtocol.Receiver, so making it extend
Thread would need some rewrite. Instead of making DataXceiver extend Thread,
this patch uses Thread.currentThread().setName(). The friendly name can be set
only after the thread starts, and that should be sufficient for this resolving
this issue.
> Improve thread naming for DataXceivers
> --------------------------------------
>
> Key: HDFS-1055
> URL: https://issues.apache.org/jira/browse/HDFS-1055
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Attachments: dataxceiver-merged.patch, dataxceiver.patch,
> hdfs-1055-branch20.txt
>
>
> The DataXceiver threads are named using the default Daemon naming, which is
> Runnable.toString(). Currently this isn't implemented, so threads have names
> like org.apache.hadoop.hdfs.server.datanode.dataxcei...@579c9a6b. It would be
> very handy for debugging (and even ops maybe) to have a better name like
> "DataXceiver for client 1.2.3.4 [reading block_234254242]"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
