[
https://issues.apache.org/jira/browse/HDDS-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076151#comment-17076151
]
Shashikant Banerjee commented on HDDS-2416:
-------------------------------------------
Thanks [~MatthewSharp] and [~cxorm] for driving this feature in Ozone. I just
looked at the design document and was thinking whether maintaining a separate
trash table in OM for keeping records of all keys which have been moved to
trash would make sense instead of just using one deleted table for all deleted
keys from active namespace.
Maintaining a separate trash table would give two advantages:
1) Listing and recovering of keys which are deleted needs to only look up the
trash table. If we maintain just one table, listing of trash keys will have to
filter which keys are in trash and which are not in trash(deleted with
skipTrash sort of option).
2) Force delete or delete with skipTrash will selectively moves the key from
the key table to deleted table while others will just be moved to Trash table.
3) Once a key expires (> Trash interval), the key will be moved from trash
table to the deleted table by a background thread and it will be deleted by the
keyDeleting service in OM.
cc ~[~msingh] [~nanda]
> Ozone Trash Feature
> -------------------
>
> Key: HDDS-2416
> URL: https://issues.apache.org/jira/browse/HDDS-2416
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Reporter: Matthew Sharp
> Assignee: Matthew Sharp
> Priority: Minor
> Attachments: Ozone_Trash_Feature.docx
>
>
> This Jira is a proposal to add a new feature to Ozone that provides a user
> with the ability to recover keys that may have been deleted accidentally.
> This would be similar to the HDFS trash feature.
>
> The attached document outlines the proposal and considerations for this
> feature.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
