[ https://issues.apache.org/jira/browse/HDFS-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089753#comment-13089753 ]
Hudson commented on HDFS-2267: ------------------------------ Integrated in Hadoop-Mapreduce-trunk #780 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/780/]) HDFS-2267. DataXceiver thread name incorrect while waiting on op during keepalive. Contributed by Todd Lipcon. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1160873 Files : * /hadoop/common/trunk/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java > DataXceiver thread name incorrect while waiting on op during keepalive > ---------------------------------------------------------------------- > > Key: HDFS-2267 > URL: https://issues.apache.org/jira/browse/HDFS-2267 > Project: Hadoop HDFS > Issue Type: Bug > Components: data-node > Affects Versions: 0.23.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Priority: Trivial > Fix For: 0.23.0 > > Attachments: hdfs-2267.txt > > > Since HDFS-941, the DataXceiver can spend time waiting for a second op to > come from the client. Currently, its thread name indicates whatever the > previous operation was, rather than something like "Waiting in keepalive for > a new request" or something. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira