Uh oh!
There was an error while loading. Please reload this page.
HDDS-15034. Query SCM status for ozone admin upgrade status command - #10084
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
dombizita
commented
Apr 20, 2026
Thank you for the review @sodonnel, addressed your comments in the latest commit. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
dombizita
commented
Apr 21, 2026
Thanks @sodonnel, based on you comments and offline discussion I agree that it's safer and easier to just get the count each time while iterating through the nodes and not store it as a counter, which could go out of sync because of corner cases |
Uh oh!
There was an error while loading. Please reload this page.
sodonnel
left a comment
There was a problem hiding this comment.
This version looks good if we get green CI.
errose28
left a comment
There was a problem hiding this comment.
Thanks for working on this @dombizita. I don't think we are quite ready to merge yet.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| for (DatanodeDetails dn : getAllNodes()) { | ||
| try { | ||
| // Only count HEALTHY nodes. STALE/DEAD nodes are intentionally excluded |
There was a problem hiding this comment.
We can put this in the javadoc for the method to indicate the nodes it is operating on. Also we should document the reasoning for allowing all operational states.
Uh oh!
There was an error while loading. Please reload this page.
* HDDS-14496-zdu: HDDS-14826. Prepare OM to switch from LayoutVersionManager to ComponentVersionManager (apache#10098) HDDS-14896. Use separate container for clients in rolling-upgrade suite (apache#10032) HDDS-15034. Query SCM status for ozone admin upgrade status command (apache#10084) HDDS-14897. Add multiple S3 gateways to the rolling-upgrade suite (apache#10028) hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OMStorage.java hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/TestOMStorage.java hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/upgrade/TestOMUpgradeFinalizer.java
What changes were proposed in this pull request?
After #10011 is merged the hardcoded placeholder responses can be removed and connect it to SCM for real values. Based on @errose28's suggestion I used HDDSLayoutVersionManager to check the finalization status of SCM and added a new counter to SCMNodeManager to keep track of the number of DNs finalized and used that for the
ozone admin upgrade statusoutput.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15034
How was this patch tested?
Added tests, green CI on my fork: https://github.com/dombizita/ozone/actions/runs/24517013218