HDDS-15051. Incorrect DN replica reporting for unhealthy and QUASI CLOSED stuck containers in Recon.#10101
Draft
devmadhuu wants to merge 2 commits intoapache:masterfrom
Draft
HDDS-15051. Incorrect DN replica reporting for unhealthy and QUASI CLOSED stuck containers in Recon.#10101devmadhuu wants to merge 2 commits intoapache:masterfrom
devmadhuu wants to merge 2 commits intoapache:masterfrom
Conversation
added 2 commits
April 18, 2026 17:48
…OSED stuck containers in Recon.
…OSED stuck containers in Recon.
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
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?
This PR fixes incorrect datanode replica details returned by Recon for unhealthy containers by switching the unhealthy-container
replicas[]response from Recon’s truncated replica history to SCM’s current replica set. The response still enriches SCM replicas with Recon history metadata like first-seen and last-seen timestamps when available, but SCM is now the source of truth for replica membership.The change adds a new S
torageContainerServiceProvider.getContainerReplicas(...)API, updatesContainerEndpointto use it for unhealthy containers, and rewrites the affected Recon endpoint tests to validate SCM-backed behavior.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15051
How was this patch tested?
TestContainerEndpointto validate the new unhealthy-container behavior against SCM-backed replica responses instead of Recon-local replica history.