[
https://issues.apache.org/jira/browse/HDDS-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641342#comment-17641342
]
Sumit Agrawal commented on HDDS-7483:
-------------------------------------
Hi [~Nibiruxu], We are thinking another approach to handle this,
Delete block is idempotent operation, so,
Approach 1:
* Delete block can be directly updated to DB, do not use transaction buffer
* And related operation while handling delete block can also be directly
updated to DB
Impact:
* Performance seems do not have impact as RocksDB also have cache.
* Since idempotent operation, if delete block called again does not have impact
Approach 2: Just a small deviation from approach 1,
* Instead of directly update rocksDB table, Can a another Buffered Batch
operation only for delete, which is managed by delete management only.
* This is have separate Buffer, and amount of changes compared to Approach 1
is less.
[~erose] [~Nibiruxu] Please suggest if its good to go above approaches...
cc: [~nanda]
> 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]
