[
https://issues.apache.org/jira/browse/HDFS-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870542#comment-16870542
]
He Xiaoqiao commented on HDFS-11242:
------------------------------------
It looks like a good idea in some ways. But I do not think we should do that,
since it could bring huge data transfer risk and destroy stability of cluster
if we provide tools to refresh network topology dynamically. IMO, we should
design more flexible rack aware script and avoid to change network topology.
> 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: [email protected]
For additional commands, e-mail: [email protected]
