-
Notifications
You must be signed in to change notification settings - Fork 597
HDDS-14966. OM UI shows wrong Leader Readiness values #10036
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Russole
wants to merge
2
commits into
apache:master
Choose a base branch
from
Russole:HDDS-14966
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+10
−5
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
leaderReadinessshould reflect readiness, but currentlyLEADER_AND_NOT_READYcannot appear in the UI in any case. If we can get correct information about the leader's readiness, we should. Otherwise we should remove the column, since it's redundant.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @adoroszlai for the review — good catch.
Currently, the UI does not have access to the actual leader readiness for each OM, so the value is derived from the node’s role. As a result, LEADER_AND_NOT_READY cannot be reflected.
We can either extend this to fetch the real leader readiness from the leader node, or consider removing the column if it is considered redundant.
This change focuses on fixing the inconsistent UI behavior across leader and follower nodes while keeping the existing semantics unchanged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should consider reverting HDDS-11726 then. BTW, the problem was also reported in the original PR: #7628 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @adoroszlai , based on the current implementation of
OzoneManagerRatisServer,getLeaderStatus()only reflects the local OM's Raft server state (via the local division), and there is no mechanism to retrieve readiness for other OM nodes.This means the UI currently does not have access to per-node leader readiness in an HA setup.
So while the original issue comes from applying the local status to all rows, the underlying limitation is that per-OM readiness is not available from the current API.
Given that, we may need to either extend the backend to expose per-node readiness, or consider removing the column if that information cannot be accurately represented.