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

   Generated-by: Claude Code (Opus 5.5)
   
   ## What changes were proposed in this pull request?
   
   `TestFailureHandlingByClient` crashes the forked test JVM when any test runs 
after `testBlockWritesWithDnFailures`.
   
   That test shuts down two datanodes, then calls `waitForBlockContainer`, 
which since HDDS-16224 polls every datanode. For a stopped datanode the volume 
DB is already closed and removed from `DatanodeStoreCache`, so 
`BlockUtils.getDB` reopens it and keeps it cached. When `restartDownDataNodes` 
restarts that datanode for the next test, loading the volume DB fails with 
`lock hold by current process`, the volume check fails its only data volume, 
and the datanode calls `ExitUtil.terminate`.
   
   Since HDDS-15749, CI for a PR that touches this class runs it by name, which 
includes the `@Flaky` test after `testBlockWritesWithDnFailures`, so the crash 
now fails CI for such PRs (e.g. #11506).
   
   The fix skips stopped datanodes in `waitForBlockContainer`.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-16982
   
   ## How was this patch tested?
   
   - Checkstyle clean.
   - 10x10 
[flaky-test-check](https://github.com/smengcl/hadoop-ozone/actions/runs/38511935985)
 on this branch (in progress). Unpatched master 
[baseline](https://github.com/smengcl/hadoop-ozone/actions/runs/38376787117): 
74/100 iterations failed, 73 of them JVM crashes.
   
   🤖 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