[
https://issues.apache.org/jira/browse/HDFS-11242?focusedWorklogId=694540&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-694540
]
ASF GitHub Bot logged work on HDFS-11242:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Dec/21 05:56
Start Date: 12/Dec/21 05:56
Worklog Time Spent: 10m
Work Description: secfree opened a new pull request #3790:
URL: https://github.com/apache/hadoop/pull/3790
### Description of PR
1. Support refreshing topology of clients/datanodes in NameNode
2. Usage: `hdfs dfsadmin -refreshTopology <ipAddr>`
3. Based on the patch `HDFS-11242.002.patch` at
https://issues.apache.org/jira/browse/HDFS-11242 with the following changes
- Rebase to `trunk`
- Change from refreshing all nodes to a specific node, as the former
holds the lock for a long time
### How was this patch tested?
1. Tested with UT
2. Tested in a real HDFS cluster
```
$ hdfs dfsadmin -fs hdfs://test -refreshTopology 1.2.3.4
Refresh topology successful at active-namenode/1.1.1.1:8020 for 1.2.3.4
Refresh topology successful at standby-namenode/1.1.1.2:8020 for 1.2.3.4
Refresh topology successful at observer-namenode/1.1.1.3:8020 for 1.2.3.4
```
### Note
1. It is also ok to pass in a hostname instead of an IP address, as keys of
the cache may be hostnames sometimes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 694540)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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: [email protected]
For additional commands, e-mail: [email protected]
