[
https://issues.apache.org/jira/browse/HDFS-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079649#comment-18079649
]
ASF GitHub Bot commented on HDFS-17915:
---------------------------------------
zhangxiping1 opened a new pull request, #8488:
URL: https://github.com/apache/hadoop/pull/8488
…ot take effect immediately.
<!--
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
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
### AI Tooling
If an AI tool was used:
- [ ] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [ ] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> Changes to the DN rack configuration on the NameNode do not take effect
> immediately.
> ------------------------------------------------------------------------------------
>
> Key: HDFS-17915
> URL: https://issues.apache.org/jira/browse/HDFS-17915
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Xiping Zhang
> Assignee: Xiping Zhang
> Priority: Major
>
> After adding a batch of DataNodes, we found that their rack information was
> incorrect and needed to be updated. However, the updated rack configuration
> did not take effect immediately after the DataNodes were restarted. Analysis
> showed that the NameNode was still caching the previous rack information, and
> the issue could only be resolved by restarting the NameNode.
> Restarting the NameNode is a costly operation, especially in very large
> clusters.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
