[
https://issues.apache.org/jira/browse/HDDS-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252665#comment-17252665
]
Lokesh Jain commented on HDDS-4370:
-----------------------------------
[~arp] Should we rely on audit log for this? Currently SCM logs the key and all
the blocks deleted for that key in audit log. SCM also logs allocatedBlock info
in the audit log. But currently for allocateBlock it is not logging the blocks
and container info. Would this logging be sufficient if we also add blocks info
in allocateBlock call?
Storing deleted blocks can be problematic in a datanode where there are
multiple close containers and block deletions. The problem can get worse if
there are small files.
> 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]
