You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Lars Francke (JIRA)" <ji...@apache.org> on 2019/06/23 08:16:00 UTC
[jira] [Commented] (HDFS-11242) Add refresh cluster network
topology operation to dfs admin
[ https://issues.apache.org/jira/browse/HDFS-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870483#comment-16870483 ]
Lars Francke commented on HDFS-11242:
-------------------------------------
This would be super useful to have.
[~reidchan] are you by any chance looking to revive this patch?
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org