ArafatKhan2198 opened a new pull request, #10492: URL: https://github.com/apache/ozone/pull/10492
## What changes were proposed in this pull request? `TestUnhealthyContainersDerbyPerformance` was taking about **336.4 seconds** in CI because it used a file-based Derby database and paid disk I/O and fsync cost on large insert/replace/delete operations. This PR speeds up the test without reducing coverage: - Switches the test to an **in-memory Derby** database (`jdbc:derby:memory:<unique-name>`) - Keeps the full **1,000,000-row** dataset and all existing assertions - Adds `@AfterAll` cleanup to drop the in-memory database - Fixes `DerbyDataSourceProvider` URL parsing so in-memory Derby URLs work, while file-based URLs remain unchanged **Why:** The test validates Recon persistence behavior at scale, not disk fsync performance. In-memory Derby removes the main bottleneck without weakening the test. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-15268 ## How was this patch tested? - Ran: ``` mvn test -Dtest=TestUnhealthyContainersDerbyPerformance -pl hadoop-ozone/recon ``` - Result: ``` [INFO] Running org.apache.hadoop.ozone.recon.persistence.TestUnhealthyContainersDerbyPerformance [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 195.8 s -- in org.apache.hadoop.ozone.recon.persistence.TestUnhealthyContainersDerbyPerformance ``` - ### Baseline was about 336.4 s; optimised run is about 195.8 s (~42% faster) -- 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]
