Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1126475583.1215630211900.JavaMail.jira@brutus>
Date: Wed, 9 Jul 2008 12:03:31 -0700 (PDT)
From: "Lohit Vijayarenu (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3720) dfsadmin -refreshNodes should re-read
 the config file.
In-Reply-To: <12214220.1215563071555.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-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lohit Vijayarenu updated HADOOP-3720:
-------------------------------------

    Attachment:     (was: HADOOP-3720-2.patch)

> dfsadmin -refreshNodes should re-read the config file.
> ------------------------------------------------------
>
>                 Key: HADOOP-3720
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3720
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.19.0
>            Reporter: Lohit Vijayarenu
>         Attachments: HADOOP-3720-1.patch, HADOOP-3720-2.patch
>
>
> hadoop dfsadmin -refreshNodes reads files defined by _dfs.hosts_ and _dfs.hosts.exclude_. If these values are not defined during namenode startup, then refreshNodes command assumes there are no files. So, while namenode is running, once cannot just edit the config file and add entries to these config variables and expect the namenode to read them. Namenode should re-read the config file for these variables (_dfs.hosts_ and _dfs.hosts.exclude_) when refreshNodes command is invoked. 

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