[ https://issues.apache.org/jira/browse/HDFS-11242?focusedWorklogId=781005&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-781005 ]
ASF GitHub Bot logged work on HDFS-11242: ----------------------------------------- Author: ASF GitHub Bot Created on: 14/Jun/22 07:17 Start Date: 14/Jun/22 07:17 Worklog Time Spent: 10m Work Description: secfree closed pull request #3790: HDFS-11242. Support refreshTopology URL: https://github.com/apache/hadoop/pull/3790 Issue Time Tracking ------------------- Worklog Id: (was: 781005) Time Spent: 50m (was: 40m) > 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.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org