[ https://issues.apache.org/jira/browse/HDFS-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245538#comment-13245538 ]
Hadoop QA commented on HDFS-3166: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12521164/HDFS-3166.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hdfs.server.namenode.TestProcessCorruptBlocks +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2169//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2169//console This message is automatically generated. > Hftp connections do not have a timeout > -------------------------------------- > > Key: HDFS-3166 > URL: https://issues.apache.org/jira/browse/HDFS-3166 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client > Affects Versions: 0.23.2, 0.23.3, 2.0.0, 3.0.0 > Reporter: Daryn Sharp > Assignee: Daryn Sharp > Priority: Critical > Attachments: HADOOP-8221.branch-1.patch, HADOOP-8221.patch, > HADOOP-8221.patch, HDFS-3166.patch, HDFS-3166.patch > > > Hftp connections do not have read timeouts. This leads to indefinitely hung > sockets when there is a network outage during which time the remote host > closed the socket. > This may also affect WebHdfs, etc. -- 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