errose28 opened a new pull request, #10098:
URL: https://github.com/apache/ozone/pull/10098
## What changes were proposed in this pull request?
This PR adds functionality and renames to prepare OM to be switched to the
new versioning framework. This PR is intended to have no impact to production
code and does not do any functional migration. It:
- Renames old layout version terminology to the new apparent version
terminology
- Adds functionality to the previously introduced `OMVersionManager` to load
upgrade actions that correspond to different versions.
- By separating upgrade action loading from the version manager itself, we
can do things like inject different upgrade actions for testing, and later bind
different upgrade actions for SCM and Datanodes even though they use the same
`HDDSVersionManager`.
- Adds testing that `OMVersionManager` can handle unknown or invalid
apparent versions on startup and fixes an issue in this area.
- Moves all upgrade finalization logic for the new framework within the
version manager. Upgrade finalizer and executor classes will not be required
and can be removed when all components are switched to the new framework.
- For OM (and later SCM), this includes the ability to finalize from a
snapshot.
## What is the link to the Apache JIRA
HDDS-14826
## How was this patch tested?
New unit tests were added for new version manager functionality like
detecting invalid versions at startup and executing upgrade actions. Existing
tests are expected to pass since the new version manager is not yet used in
prod code.
--
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]