[
https://issues.apache.org/jira/browse/HDDS-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511622#comment-17511622
]
Jyotinder Singh commented on HDDS-6414:
---------------------------------------
As discussed
[here|https://github.com/apache/ozone/pull/3227#discussion_r833542316]
Please remove the workarounds in TestRootedOzoneFileSystem.java and
TestRootedOzoneFileSystemWithFSO.java as a part of this patch.
I have marked all such lines of code with a comment saying "HDDS-6414" to make
it easier to replace them.
> 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]
