[ 
https://issues.apache.org/jira/browse/HDDS-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451267#comment-17451267
 ] 

Attila Doroszlai commented on HDDS-5993:
----------------------------------------

Reproduced this once with debug log:

{code}
[OM StateMachine ApplyTransaction Thread - 0] DEBUG key.OMKeysDeleteRequest 
(OMKeysDeleteRequest.java:validateAndUpdateCache(219)) - Keys delete success. 
Volume:vol-0-35158, Bucket:bucket-1-56461, 
Keys:key-0-09889,key-1-00902,key-2-53642,key-3-27817,key-4-41070,key-5-34109,key-6-52678,key-7-53474,key-8-39001,key-9-06421
...
[OM StateMachine ApplyTransaction Thread - 0] DEBUG 
bucket.OMBucketDeleteRequest 
(OMBucketDeleteRequest.java:validateAndUpdateCache(124)) - bucket: 
bucket-1-56461 is not empty 
{code}

Still trying to reproduce it one more time with an additional debug message to 
see why the bucket is considered not empty.

> Intermittent failure in TestRandomKeyGenerator#cleanObjectsTest
> ---------------------------------------------------------------
>
>                 Key: HDDS-5993
>                 URL: https://issues.apache.org/jira/browse/HDDS-5993
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ethan Rose
>            Priority: Major
>         Attachments: it-ozone.zip
>
>
> Failed on these CI runs from master:
> [https://github.com/apache/ozone/runs/4202214499]
> [https://github.com/apache/ozone/runs/4193743413]
>  
>  
> {code:java}
>  java.lang.RuntimeException: VOLUME_NOT_EMPTY 
> org.apache.hadoop.ozone.om.exceptions.OMException:    2803 at 
> org.apache.hadoop.ozone.freon.RandomKeyGenerator.call(RandomKeyGenerator.java:378)
>     2804 at 
> org.apache.hadoop.ozone.freon.TestRandomKeyGenerator.cleanObjectsTest(TestRandomKeyGenerator.java:191)
>  {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to