smengcl opened a new pull request, #11673:
URL: https://github.com/apache/ozone/pull/11673

   Generated-by: Claude Code (Opus 5.5)
   
   ## What changes were proposed in this pull request?
   
   `test-repair-tools.sh` fails intermittently with:
   
   ```
   Waiting for container 'ozonesecure-ha-om1-1' to stop...
   Timeout: Container 'ozonesecure-ha-om1-1' did not stop within 60 seconds.
   ```
   
   `ratis-transaction-repair.robot` uses Byteman to make each OM terminate from 
its apply transaction thread. The OM shutdown hook then blocks in 
`omRatisServer.stop()` until the shutdown hook timeout 
(`ozone.service.shutdown.timeout`, default 60s) fires. This also happens in 
green `master` runs, so each OM container needs a bit over 60s to exit, while 
`repair_and_restart_om` waits at most 60s. The test passes only when the wait 
starts a few seconds after the crash. In the failed run, JVM pauses on the 
runner made the hook time out 62s after the crash, so the wait expired first.
   
   This PR raises the wait to 120s so it covers the shutdown hook timeout.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-17288
   
   ## How was this patch tested?
   
   - Compared OM logs from the failed run with a green `master` run: in both, 
every OM logs `ShutdownHook ... timeout` about 60s after `Terminating with exit 
status 1`.
   - 10x 
[repeat-acceptance](https://github.com/smengcl/hadoop-ozone/actions/runs/39686223257)
 of `ozonesecure-ha/test-repair-tools.sh` 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]

Reply via email to