Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 7 May 2012 18:42:52 +0000 (UTC)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1151832403.35748.1336416172248.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <382913428.30866.1336252310682.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3376) DFSClient fails to make connection
 to DN if there are many unusable cached sockets
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans commented on HDFS-3376:
-------------------------------------------

Hey Todd,

I have been trying to follow some of the fixes you have been putting into the HDFS socket caching.  I was wondering if you would be willing to pull HDFS-3357 and this one, HDFS-3376, into branch-0.23.  They both seem to apply cleanly, but I am not an HDFS committer to do this myself.
                
> DFSClient fails to make connection to DN if there are many unusable cached sockets
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-3376
>                 URL: https://issues.apache.org/jira/browse/HDFS-3376
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: hdfs-3376.txt
>
>
> After fixing the datanode side of keepalive to properly disconnect stale clients, (HDFS-3357), the client side has the following issue: when it connects to a DN, it first tries to use cached sockets, and will try a configurable number of sockets from the cache. If there are more cached sockets than the configured number of retries, and all of them have been closed by the datanode side, then the client will throw an exception and mark the replica node as dead.

--
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