[
https://issues.apache.org/jira/browse/HDFS-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868588#comment-17868588
]
ruiliang commented on HDFS-11242:
---------------------------------
The correct process for adding a new node with the correct mapping is:
1. Update the topology file of the new DN.
2. Issue dfadmin-refreshnodes to update the new topology map in the NN.
3. Start DN only after (2) so that it picks up the correct mapping and the
default mapping is not cached.
> Add refresh cluster network topology operation to dfs admin
> -----------------------------------------------------------
>
> Key: HDFS-11242
> URL: https://issues.apache.org/jira/browse/HDFS-11242
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.0.0-alpha1
> Reporter: Reid Chan
> Priority: Minor
> Labels: pull-request-available
> Attachments: HDFS-11242.002.patch, HDFS-11242.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The network topology and dns to switch mapping are initialized at the start
> of the namenode.
> If admin wants to change the topology because of new datanodes added, he has
> to stop and restart namenode(s), otherwise those new added datanodes are
> squeezed under /default-rack.
> It is a low frequency operation, but it should be operated appropriately, so
> dfs admin should take the responsibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
