[
https://issues.apache.org/jira/browse/HDFS-16368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039512#comment-18039512
]
ASF GitHub Bot commented on HDFS-16368:
---------------------------------------
github-actions[bot] commented on PR #3743:
URL: https://github.com/apache/hadoop/pull/3743#issuecomment-3555188380
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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, namenode
> Affects Versions: 2.7.7, 3.3.1
> Reporter: farmmamba
> Assignee: farmmamba
> Priority: Major
> Labels: features, pull-request-available
> Attachments: 0001.patch
>
> Time Spent: 40m
> 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.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
