Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <5358027.1189032814230.JavaMail.jira@brutus>
Date: Wed, 5 Sep 2007 15:53:34 -0700 (PDT)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1138) Datanodes that are dead for a long
 long time should not show up in the UI
In-Reply-To: <21115675.1174516772142.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525247 ] 

Hadoop QA commented on HADOOP-1138:
-----------------------------------

+1

http://issues.apache.org/jira/secure/attachment/12365214/HADOOP-1138.patch applied and successfully tested against trunk revision r573081.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/693/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/693/console

> Datanodes that are dead for a long long time should not show up in the UI
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-1138
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1138
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: Raghu Angadi
>             Fix For: 0.15.0
>
>         Attachments: HADOOP-1138.patch, HADOOP-1138.patch, HADOOP-1138.patch
>
>
> Proposal 1:
> If a include files is used, then show all nodes (dead/alive) that are listed in the includes file. If there isn't an include file, then display only nodes that have pinged this instance of the namenode.
> Proposal2:
> A config variable specifies the time duration. The namenode, on a restart, purges all datanodes that have not pinged for that time duration. The default value of this config variable can be 1 week. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.