arunsarin85 opened a new pull request, #10270: URL: https://github.com/apache/ozone/pull/10270
## What changes were proposed in this pull request? Wait until Recon’s container key index reflects the written key (using TestReconOmMetaManagerUtils.waitUntilReconKeyCounts) after OM sync, resolve the container id from the elected OM leader via lookupKey, remove the @Flaky marker. Please describe your PR in detail: The test failed when the container key table was still empty after waitForEventBufferEmpty, so the iterator never set reconKeyPrefix and the assertion saw null. The event buffer can drain before Recon finishes applying container key updates, which is already documented on waitUntilReconKeyCounts. The test now takes the container id from the current OM leader (not getOzoneManager(), which is only the first OM in the HA list), calls waitUntilReconKeyCounts for that container, then asserts the key prefix. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-15221 ## How was this patch tested? Ran flaky-test check on master and HDDS-15221 branch [with fix] - master [without fix] - https://github.com/arunsarin85/ozone/actions/runs/25848486126 - HDDS-15221[with fix] - https://github.com/arunsarin85/ozone/actions/runs/25863147571 -- 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]
