Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sun, 11 Aug 2013 22:44:48 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12644597.1366895637329.43229.1376261088605@arcas>
In-Reply-To: <JIRA.12644597.1366895637329@arcas>
References: <JIRA.12644597.1366895637329@arcas>
Subject: [jira] [Commented] (HDFS-4754) Add an API in the namenode to mark a
 datanode as stale
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas commented on HDFS-4754:
---------------------------------------

Early comments. DFS_NAMENODE_MARK_STALE_MAX_DURATION_KEY and semantics of marking a node until certain period, why is this required? Datanode will automatically be marked non-stale on a heartbeat right? Also I am not sure this API should be in HdfsAdmin API. Can you describe which API will be used by HBase and where will HdfsAdmin be used?

                
> Add an API in the namenode to mark a datanode as stale
> ------------------------------------------------------
>
>                 Key: HDFS-4754
>                 URL: https://issues.apache.org/jira/browse/HDFS-4754
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client, namenode
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>            Priority: Critical
>             Fix For: 3.0.0, 2.1.1-beta
>
>         Attachments: 4754.v1.patch, 4754.v2.patch, 4754.v4.patch, 4754.v4.patch
>
>
> There is a detection of the stale datanodes in HDFS since HDFS-3703, with a timeout, defaulted to 30s.
> There are two reasons to add an API to mark a node as stale even if the timeout is not yet reached:
>  1) ZooKeeper can detect that a client is dead at any moment. So, for HBase, we sometimes start the recovery before a node is marked staled. (even with reasonable settings as: stale: 20s; HBase ZK timeout: 30s
>  2) Some third parties could detect that a node is dead before the timeout, hence saving us the cost of retrying. An example or such hw is Arista, presented here by [~tsuna] http://tsunanet.net/~tsuna/fsf-hbase-meetup-april13.pdf, and confirmed in HBASE-6290.
> As usual, even if the node is dead it can comeback before the 10 minutes limit. So I would propose to set a timebound. The API would be
> namenode.markStale(String ipAddress, int port, long durationInMs);
> After durationInMs, the namenode would again rely only on its heartbeat to decide.
> Thoughts?
> If there is no objections, and if nobody in the hdfs dev team has the time to spend some time on it, I will give it a try for branch 2 & 3.

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