[
https://issues.apache.org/jira/browse/HDDS-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252931#comment-17252931
]
Arpit Agarwal commented on HDDS-4370:
-------------------------------------
Hi [~ljain], yes audit log may be sufficient if it tells us which blocks were
deleted on which nodes. However audit log will likely be rotated after a few
days.
I may be misunderstanding something, storing deleted block info should not be
problematic right? We aren't storing the block data itself, just metadata about
which blocks were deleted which should be quite minimal.
> 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]
