smengcl opened a new pull request, #11701: URL: https://github.com/apache/ozone/pull/11701
Generated-by: Claude Code (Opus 5.5) ## What changes were proposed in this pull request? `TestBackgroundContainerMetadataScannerIntegration#testCorruptionDetected` intermittently times out in `ContainerScannerIntegrationTests#closeContainerAndWait`, which gives the datanode only 5 seconds to report the container CLOSED. The close is applied through Ratis, and `KeyValueContainer#close` calls `flushAndSyncDB`, which fsyncs the RocksDB WAL. In the failed run the close was requested at 11:32:56.5. At the timeout (11:33:01.5) the thread dump shows the `ContainerOp` thread still in `RocksDB.flushWal` under `KeyValueContainer.close`. The container closed at 11:33:03.0, about 6.5 seconds after the request. Even the first close in that run took about 3 seconds, so 5 seconds leaves too little headroom on a slow CI disk. This PR raises that wait to 30 seconds. The wait polls, so passing runs are not slowed down. The helper is shared by all container scanner integration tests, so they all get the fix. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-17346 ## How was this patch tested? This only changes a timeout, so the race is not removed by construction: a datanode fsync slower than 30 seconds would still fail the test. One green run cannot prove the test is no longer flaky. - `mvn -pl :ozone-integration-test -am test -Dtest=TestBackgroundContainerMetadataScannerIntegration`: 6/6 passed - 10x10 [flaky-test-check](https://github.com/smengcl/hadoop-ozone/actions/runs/39837496479) on this branch: in progress 🤖 Generated with [Claude Code](https://claude.com/claude-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]
