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 2023/06/22 20:52:00 UTC
[jira] [Updated] (HDDS-8579) [Snapshot] Allow a bucket to be deleted once all snapshots on it are deleted even if not all are reclaimed
[ https://issues.apache.org/jira/browse/HDDS-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prashant Pogde updated HDDS-8579:
---------------------------------
Parent Issue: HDDS-8544 (was: HDDS-6517)
> [Snapshot] Allow a bucket to be deleted once all snapshots on it are deleted even if not all are reclaimed
> ----------------------------------------------------------------------------------------------------------
>
> Key: HDDS-8579
> URL: https://issues.apache.org/jira/browse/HDDS-8579
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Siyao Meng
> Priority: Major
>
> In HDDS-6984, a check is added that prevents a bucket from being deleted if any snapshot info entry exists in snapshotInfoTable:
> https://github.com/apache/ozone/commit/52103f273a186b1b3f1b0390e2363af3d45c2618#diff-d08050bb16c72a13afe3b3ae5c5eab39132130118adc1bdc0f64b86300f73a10R219-R255
> As [~sumit.aga@gmail.com] recently brought up, this check might be too restrictive.
> We can possibly relax the condition that so even if there are deleted snapshots that still needs to be reclaimed, we will *allow* the bucket entry deletion, *as long as there are no ACTIVE snapshots* on the bucket anymore. (Just need to double check if we utilize active DB's bucketTable in SnapshotDeletingTask, use snapshot's bucketTable if so. [~aswinshakil])
> cc [~sshenoy], [~sumit.aga@gmail.com]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org