[
https://issues.apache.org/jira/browse/HDDS-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722851#comment-17722851
]
Uma Maheswara Rao G commented on HDDS-4966:
-------------------------------------------
Can we resolve this if we are not seeing this symptoms ?
> Disk space leak after deleting Ozone files
> ------------------------------------------
>
> Key: HDDS-4966
> URL: https://issues.apache.org/jira/browse/HDDS-4966
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Wei-Chiu Chuang
> Priority: Critical
>
> Sometimes deleting Ozone files does not remove containers and block files at
> all. Even removing the bucket doesn't reclaim the space. I even forcefully
> closed all the containers.
> Due to HDDS-2534, there is no way to delete the dangling containers manually.
> What makes it even more perplexing is that some containers are no longer in
> SCM's record (ozone admin container list couldn't find the container) but the
> container replica are still (including block files and metadata) on the DNs.
> Looking at OM's rocksdb instance, keyTable is empty, bucketTable is empty.
> prefixKeyTable
> empty. But openKeyTable is not.
> The application that generated the data (teragen) was killed. I don't think
> the clients are still connected and the openKeyTable is not pruned after a
> day.
> Maybe we shouldn't prune openKeyTable when deleting the corresponding
> volume/bucket?
> Unfortunately, it happens from time to time but i can't reliably reproduce.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
