[
https://issues.apache.org/jira/browse/HDDS-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754772#comment-17754772
]
Prashant Pogde commented on HDDS-8579:
--------------------------------------
Such an optimization can open a can of worms. What do we do if someone deletes
the buckets and recreates the bucket with the same name while there are still
snapshots in snapshot info table refereing to the same bucket name.
I guess there is little return in solving various complex cases in handling
this. Marking this as won't do for now.
> [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 [[email protected]] 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], [[email protected]]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
