[
https://issues.apache.org/jira/browse/HDFS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-22.
-------------------------
Resolution: Not A Problem
The current docs:
{code}
Updates the set of hosts allowed to connect to namenode. Re-reads the config
file to update values defined by dfs.hosts and dfs.host.exclude and reads the
entires (hostnames) in those files. Each entry not defined in dfs.hosts but in
dfs.hosts.exclude is decommissioned. Each entry defined in dfs.hosts and also
in dfs.host.exclude is stopped from decommissioning if it has aleady been
marked for decommission. Entires not present in both the lists are
decommissioned.
{code}
Covers it pretty much I think? Please reopen if not.
> Help information of refreshNodes does not show how to decomission nodes
> -----------------------------------------------------------------------
>
> Key: HDFS-22
> URL: https://issues.apache.org/jira/browse/HDFS-22
> Project: Hadoop HDFS
> Issue Type: Bug
> Environment: hadoop 0.19.1, jdk 1.6, CentOS 5.2
> Reporter: Wang Xu
> Assignee: Wang Xu
> Attachments: refreshNodes.patch
>
>
> The help information does not indicate how to decommission nodes.
> It only describes two scenarios:
> * to stop nodes if not in dfs.hosts
> * stop decommissioning if node is decommissioning and in both dfs.hosts and
> dfs.host.exclude
> but omits this one:
> * starting decommissioning if node is in service and in both dfs.hosts and
> dfs.host.exclude
> It would better describe as "Each entry defined in dfs.hosts and also
> in dfs.host.exclude is start decommissioning and start block replication
> if it is in service, or is stopped from decommissioning if it has already
> been marked for decommission."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
