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 "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/12/12 05:13:00 UTC

[jira] [Updated] (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:all-tabpanel ]

ASF GitHub Bot updated HDFS-11242:
----------------------------------
    Labels: pull-request-available  (was: )

> 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: 10m
>  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.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org