You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Prashant Pogde (Jira)" <ji...@apache.org> on 2022/06/09 14:49:00 UTC

[jira] [Assigned] (HDDS-6857) Implement Snapshot Delete API

     [ https://issues.apache.org/jira/browse/HDDS-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prashant Pogde reassigned HDDS-6857:
------------------------------------

    Assignee:     (was: Prashant Pogde)

> Implement Snapshot Delete API
> -----------------------------
>
>                 Key: HDDS-6857
>                 URL: https://issues.apache.org/jira/browse/HDDS-6857
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Manager
>    Affects Versions: 1.3.0
>            Reporter: Prashant Pogde
>            Priority: Major
>
> This Jira can be used to track all the tasks associated with Deleting a Snapshot.
> Snapshot Delete would also be driven through a RATIS transaction.
> This API should move Snapshot from Active State to Deleted State. We should not remove the Snapshot RocksDB checkpoint directory yet. 
> There will be another background thread that should reclaim all the keys that will go orphan as part of Snapshot deletion.
> The Snapshot should move to a deleted-and-reclaimed state only after all such would-be-orphan keys and their data blocks are deleted.
>  
> The design doc has details on how to identify would-be-orphan key-set when the snapshot gets deleted.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org