[
https://issues.apache.org/jira/browse/HDFS-16368?focusedWorklogId=689088&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-689088
]
ASF GitHub Bot logged work on HDFS-16368:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Dec/21 08:50
Start Date: 02/Dec/21 08:50
Worklog Time Spent: 10m
Work Description: hfutatzhanghb opened a new pull request #3743:
URL: https://github.com/apache/hadoop/pull/3743
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Currently in HDFS, if we update the rack info for rack-awareness, we may
need to rolling restart namenodes to let it be effective. If cluster is large,
the cost time of rolling restart namenodes is very log. So, we develope a
method to refresh topology info without rolling restart namenodes.
### How was this patch tested?
1. hdfs dfsamin -printTopology
2. upload a file to HDFS, then use `fsck` to check its block location and
rack info.
### For code changes:
https://issues.apache.org/jira/browse/HDFS-16368
--
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: 689088)
Remaining Estimate: 0h
Time Spent: 10m
> DFSAdmin supports refresh topology info without restarting namenode
> --------------------------------------------------------------------
>
> Key: HDFS-16368
> URL: https://issues.apache.org/jira/browse/HDFS-16368
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: dfsadmin, namanode
> Affects Versions: 2.7.7, 3.3.1
> Reporter: zhanghaobo
> Priority: Major
> Labels: features, pull-request-available
> Attachments: 0001.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently in HDFS, if we update the rack info for rack-awareness, we may need
> to rolling restart namenodes to let it be effective. If cluster is large, the
> cost time of rolling restart namenodes is very log. So, we develope a method
> to refresh topology info without rolling restart namenodes.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
