HDDS-15853. [Recon] Show error card for unavailable datanode in Cluster Capacity#10767
Open
priyeshkaratha wants to merge 1 commit into
Open
HDDS-15853. [Recon] Show error card for unavailable datanode in Cluster Capacity#10767priyeshkaratha wants to merge 1 commit into
priyeshkaratha wants to merge 1 commit into
Conversation
priyeshkaratha
marked this pull request as ready for review
July 15, 2026 02:11
chihsuan
approved these changes
Jul 15, 2026
chihsuan
left a comment
chihsuan
left a comment
Contributor
There was a problem hiding this comment.
Thanks @priyeshkaratha LGTM. Tested locally as well.
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?
On the Recon Cluster Capacity page, the datanode detail card seeds its default selection to the first datanode in the filtered list, regardless of whether that DN is reachable. When the default-selected DN is unavailable — its pending-deletion query failed, signalled by the
pendingBlockSize === -1sentinel — the card still renderedused/remaining/committedvalues from the storage report. For an offline or unreachable DN these values can be stale, so the UI silently displayed outdated capacity data. The node-selector dropdown already disables such DNs (disabledOpts), but the default seeding (hostNames[0]) can still land on one.This PR surfaces an error state for the selected DN instead of showing potentially outdated data, reusing the error-card pattern introduced for the SCM failure case in HDDS-15272 (#10411)
Note : Code is generated using AI
What is the link to the Apache JIRA
HDDS-15853
How was this patch tested?
Tested manually and updated unit test case
