[
https://issues.apache.org/jira/browse/HDDS-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259020#comment-17259020
]
Ethan Rose commented on HDDS-4370:
----------------------------------
If we agree that we do not want to store deleted block data in RocksDB, I can
make a new Jira to clean up some dead code. I believe the deleted blocks table
and corresponding chunk info list codec are not being used now.
> Datanode deletion service can avoid storing deleted blocks
> ----------------------------------------------------------
>
> Key: HDDS-4370
> URL: https://issues.apache.org/jira/browse/HDDS-4370
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Lokesh Jain
> Assignee: Aryan Gupta
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> Currently BlockDeletingService in datanode processes the blocks to be deleted
> and then stores them in a deleted blocks table. We can avoid storing deleted
> blocks in the container rocksDB.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
