[AMBARI-26616] Refresh rack topology mappings upon DataNode or NodeManager install#4139
Open
goyalanurag wants to merge 4 commits into
Open
[AMBARI-26616] Refresh rack topology mappings upon DataNode or NodeManager install#4139goyalanurag wants to merge 4 commits into
goyalanurag wants to merge 4 commits into
Conversation
Contributor
|
@goyalanurag thanks for reporting on this, approach looks good to me.. could you please add the UT for this and attach manual test snippets.? |
Author
|
I have update the description with some screenshots. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
When adding DataNode or NodeManager hosts, Ambari refreshes include/exclude files on NameNode and ResourceManager hosts, but the rack topology mapping file can remain stale because topology regeneration only runs on hosts where worker components are started. This requires restarting NameNode or ResourceManager before new hosts appear with the correct rack information.
Update the HDFS and YARN refresh/decommission workflows to regenerate
topology_mappings.dataduring the existingUpdate Include/Exclude Filesaction, sohdfs dfsadmin -printTopology,hdfs dfsadmin -report, andyarn node -statusreflect newly added hosts without restarting master components.How was this patch tested?
Tested manually multiple times by adding DataNodes and NodeManagers to Hadoop cluster.
Below screenshots are before/after adding a worker (DataNode + NodeManager) to cluster.
Before Adding Worker
After Adding Worker