errose28 opened a new pull request, #9723:
URL: https://github.com/apache/ozone/pull/9723

   ## What changes were proposed in this pull request?
   
   The prepare for upgrade step will not work in the context of ZDU. The design 
doc outlines a plan to upgrade the OMs without this command, so we can remove 
it from the ZDU feature branch. Since this is going in a branch, it is ok that 
we have not yet implemented the OM versioning required for guaranteed 
consistency without prepare for upgrade.
   
   In this change, prepare for upgrade handling is removed from the server in a 
backwards compatible way. If the server receives a prepare request, it will 
return success but indicate that it is not supported in this server version. 
The CLI has been hidden on the client side, but left intact in case the new 
client is used to upgrade an old server.
   
   After v100 for ZDU is added, we can add an upgrade action which clears the 
DB key and prepare marker file that may be left behind in the old version.
   
   In the next major Ozone release following this change (3.0?), we can remove 
support for the CLI and OM API entirely.
   
   ## What is the link to the Apache JIRA
   
   HDDS-14580
   
   ## How was this patch tested?
   
   - Passing run on my 
[fork](https://github.com/errose28/ozone/actions/runs/22244868758/job/64356595280)
   
   - New tests for the expected backwards compatible prepare functionality 
added in `TestOzoneShellHA` and `TestOzoneManagerRequestHandler.java‎`
     - Some hsync/open file tests had existing issues causing them to fail when 
the new prepare test was added. These have been marked unhealthy and the 
resolution is tracked in HDDS-14686.
   - Existing tests should pass indicating no dependency on prepare
   - There was an existing bug in `PrepareSubCommand` where the client object 
used to check each OM for status had no port explicitly configured, and was 
falling back to the default. This usually worked, but had never been tested 
with MiniOzoneCluster, where the ports are randomly assigned. The command had 
to be updated to account for the configured OM port due to the new 
MiniOzoneCluster test added.
   - `TestOMUpgradeFinalization` was removed because it depended on prepare to 
force a follower to install a snapshot. We can add a new test that covers this 
functionality in HDDS-14687.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to