[
https://issues.apache.org/jira/browse/HDFS-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870574#comment-16870574
]
He Xiaoqiao commented on HDFS-11242:
------------------------------------
Thanks [~larsfrancke] for your doubt and the detailed comments.
For the situation you said above, I think the proper way is:
a. clean CachedDNSToSwitchMapping#cache complete or just clean one host. (which
do not support currently).
b. fix the bug via Consul (sorry I am not familiar with that).
c. stop DataNode and better to wait for proper time (630s by default which
namenode consider datanode dead) then start DataNode.
Please correct me if something wrong.
I want to state that change network topology / rack aware script is very risky.
We should change it cautiously. especially for large cluster. FYI.
> 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
> Attachments: HDFS-11242.002.patch, HDFS-11242.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
