Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 23 Oct 2012 15:31:14 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <29400779.16302.1351006274257.JavaMail.jiratomcat@arcas>
In-Reply-To: <886579078.90549.1343041534998.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3704) In the DFSClient, Add the node to
 the dead list when the ipc.Client calls fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daryn Sharp commented on HDFS-3704:
-----------------------------------

I too am concerned about marking the node dead for any {{IOException}}.  Transient errors won't be recoverable.  Perhaps a {{RemoteException}} that isn't a {{ReplicaNotFoundException}} are candidates for marking the dead as node, but I'm not well acquainted with the code to know what unexpected consequences it may have. 
                
> In the DFSClient, Add the node to the dead list when the ipc.Client calls fails
> -------------------------------------------------------------------------------
>
>                 Key: HDFS-3704
>                 URL: https://issues.apache.org/jira/browse/HDFS-3704
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 1.0.3, 2.0.0-alpha
>            Reporter: nkeywal
>            Priority: Minor
>         Attachments: HADOOP-3704.patch, HADOOP-3704.patch
>
>
> The DFSCLient maintains a list of dead node per input steam. When creating this DFSInputStream, it may connect to one of the nodes to check final block size. If this call fail, this datanode should be put in the dead nodes list to save time. If not it will be retried for the block transfer during the read, and we're likely to get a timeout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira