[
https://issues.apache.org/jira/browse/HDFS-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270474#comment-13270474
]
Hudson commented on HDFS-3375:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1073 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1073/])
HDFS-3375. Put client name in DataXceiver thread name for readBlock and
keepalive. Contributed by Todd Lipcon. (Revision 1335270)
Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1335270
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java
> Put client name in DataXceiver thread name for readBlock and keepalive
> ----------------------------------------------------------------------
>
> Key: HDFS-3375
> URL: https://issues.apache.org/jira/browse/HDFS-3375
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Affects Versions: 2.0.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: hdfs-3375.txt
>
>
> Currently the datanode thread names include the client for write operations,
> but not for read. We should include the client name for read ops.
> Additionally, in the keepalive phase, we should include the client name that
> initiated the previous request as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
