Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 22 Oct 2012 11:48:14 +0000 (UTC)
From: "Yanbo Liang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <996473850.9420.1350906494693.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=13481316#comment-13481316 ] 

Yanbo Liang commented on HDFS-3704:
-----------------------------------

If the ipc.Client calls to DataNode fails, maybe it was caused by temporary failure and will recovery later. If we treat these DataNodes as failure nodes corresponding to this DFSInputStream, we can not use replicas on these kind of DataNode no longer even if they recover from failure at later time. Does it meet the requirement of other workflow?
                
> 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
>
> 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