[
https://issues.apache.org/jira/browse/HDDS-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511390#comment-17511390
]
Jyotinder Singh commented on HDDS-6414:
---------------------------------------
While working on HDDS-6425, we found contract tests that were erroneously
passing due to a gap in OmMetadataManagerImpl#isBucketEmpty implementation.
These test cases have [currently been commented
out|https://github.com/apache/ozone/pull/3227/files#diff-3a8566cc32e4962cc3eefe8f0947b66ac313c27971feb9e159e9a7d4b4f3731cR63-R75]
as a part of HDDS-6425 since they are now failing after the fix.
The two test cases are
ITestRootedOzoneContractRootDir#testRmEmptyRootDirNonRecursive
ITestRootedOzoneContractRootDir#testListEmptyRootDirectory
They should be enabled once the patch for HDDS-6414 is implemented.
> Ozone doesn’t reclaim space after deletion of volume via ofs
> ------------------------------------------------------------
>
> Key: HDDS-6414
> URL: https://issues.apache.org/jira/browse/HDDS-6414
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sadanand Shenoy
> Assignee: Sadanand Shenoy
> Priority: Major
> Labels: pull-request-available
>
> # Create a volume ,FSO bucket and write some keys
> # Delete volume via ozone fs -rm ofs://serviceId/volname
> This creates an OmKeysDeleteRequest which returns bucket layout as LEGACY for
> that particular class, therefore for deletion the KeyTable is checked
> instead of FileTable and this is why omKeyInfo is returned null.
> {code:java}
> Received a request to delete a Key does not exist
> /testingoozne/benchmarks/output/ {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]
