[ https://issues.apache.org/jira/browse/HDFS-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031382#comment-14031382 ]
Hudson commented on HDFS-6529: ------------------------------ SUCCESS: Integrated in Hadoop-trunk-Commit #5705 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5705/]) HDFS-6529. Trace logging for RemoteBlockReader2 to identify remote datanode and file being read. Contributed by Anubhav Dhoot. (atm: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1602538) * /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/RemoteBlockReader2.java > Trace logging for RemoteBlockReader2 to identify remote datanode and file > being read > ------------------------------------------------------------------------------------ > > Key: HDFS-6529 > URL: https://issues.apache.org/jira/browse/HDFS-6529 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs-client > Affects Versions: 2.4.0 > Reporter: Anubhav Dhoot > Assignee: Anubhav Dhoot > Priority: Minor > Fix For: 2.5.0 > > Attachments: HDFS-6529.patch > > > The scenario is some download is stuck and we dont know which data node is > the client waiting and for which path. > By turning this file trace logging we will get a running trace of which > requests have started and which have completed. > If trace is not enabled, there is no overhead other than checking if trace is > enabled -- This message was sent by Atlassian JIRA (v6.2#6252)