[
https://issues.apache.org/jira/browse/HDDS-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641710#comment-17641710
]
Sumit Agrawal commented on HDDS-7483:
-------------------------------------
Thanks [~erose] [~Nibiruxu] , I agree your point.
Currently for Container and other operation, we are maintaining the memory, and
not depending on transaction buffer to support DN operation.
So we can have memory of blocks to be deleted, but this will consume a lot of
memory if blocks are huge. *+I am exploring one way+* provided by RocksDB to
query from transaction Buffer itself to reuse rocksDB data.
[https://rocksdb.org/blog/2015/02/27/write-batch-with-index.html]
Any opinion of having any risk with this approach?
> DN do not remove blocks for deleted content
> -------------------------------------------
>
> Key: HDDS-7483
> URL: https://issues.apache.org/jira/browse/HDDS-7483
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Major
>
> When delete directory and files is performed, its not deleted in local disk
> of DN.
>
> # SCM keeps transaction information in buffer and commits to DB after a set
> of transaction (like 10,000)
> # DeleteBlockService on SCM gets information from rocks DB and its not
> available as its present in buffer, so delete list size is empty
> This may needs resolve to delete blocks from DN if its already ready for
> deletion.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
