Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 2 Apr 2012 18:57:23 +0000 (UTC)
From: "Hadoop QA (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1205891781.2037.1333393043887.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3166) Hftp connections do not have a
 timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244450#comment-13244450 ] 

Hadoop QA commented on HDFS-3166:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12520632/HADOOP-8221.branch-1.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 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2153//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
>
>
> 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