HDDS-10215. Speed up some tests that use OmTestManagers #6107
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?
Some of the slowest unit tests use
OmTestManagersto launch OM. It takes ~10 seconds to initialize (half of that is Ratis leader election). The test cases are pretty quick after that.This change speeds up four of these tests, mostly by converting per-method setup to per-class, to reduce the overhead.
Also, wait for OM leader election before proceeding with the test, to avoid an exception related to failover retry while trying to create the RPC client.
Use test method name as volume name to avoid conflicts, and unexpected number of buckets/keys.
Some of the assertions need to be tweaked to account for objects left over and operations performed by other test cases.
https://issues.apache.org/jira/browse/HDDS-10215
How was this patch tested?
https://github.com/adoroszlai/ozone/actions/runs/7670459056/job/20907076486