[
https://issues.apache.org/jira/browse/HDFS-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanping Wang updated HDFS-1703:
-------------------------------
Attachment: HDFS-1703.patch
The new startup script has the following changed behavior:
# Old behavior:
#* startup script had to be run on primary namenode. The script started
namenode on the the node where it was run. Secondary namenode was started on
the node in "master" file.
#* Datanodes were started on nodes that are in "slaves" file.
# New behavior:
#* Script determines namenodes and secondary namenodes from the hdfs-site.xml
configuration and starts appropriate nodes on these machines. The file "master"
is no longer required.(Changed behavior)
#* Datanodes were started on nodes that are in "slaves" file. (No change)
Installation using their own scripts can start the nodes, based on the example
in this script.
Decommission tool:
# Two new scripts are added for performing decommissioning in federation setup.
Combined all the scripts change into one patch, HDFS-1703.patch
> HDFS federation: Improve start/stop scripts and add script to decommission
> datanodes
> ------------------------------------------------------------------------------------
>
> Key: HDFS-1703
> URL: https://issues.apache.org/jira/browse/HDFS-1703
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: scripts
> Affects Versions: Federation Branch
> Reporter: Tanping Wang
> Assignee: Tanping Wang
> Priority: Minor
> Fix For: Federation Branch
>
> Attachments: HDFS-1703.patch
>
>
> This Jira covers two issues:
> # Startup scripts should start namenodes, secondary namenodes and datanodes
> on hosts retunred by getConfig (new feature). This patch is spread out to
> both common(HADOOP-7179) and hdfs (this Jira).
> # Decommission script to decommission datanodes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
