[
https://issues.apache.org/jira/browse/HDDS-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sadanand Shenoy updated HDDS-6414:
----------------------------------
Description:
# 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}
getBucketLayout() should return the correct bucketLayout based on the bucket.
was:
# 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,
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}
> 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: Bug
> Reporter: Sadanand Shenoy
> Priority: Major
>
> # 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}
> getBucketLayout() should return the correct bucketLayout based on the bucket.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
