[
https://issues.apache.org/jira/browse/HDDS-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemant Kumar updated HDDS-11705:
--------------------------------
Release Note:
Ozone did not support snapshots on linked buckets before this release. However,
a user could have inadvertently created snapshots on linked buckets. Hence when
upgrading from an older version that doesn't support snapshots on linked
buckets to a newer version that supports snapshots on linked buckets, it is
essential to ensure that there are no snapshots on linked buckets otherwise
they will linger around. If there are any snapshots on linked buckets, those
snapshots need to be deleted by using snapshot delete command:
ozone sh snapshot delete <vol>/<linked bucket name> <snapshot name>
> Snapshot operations on linked buckets should work on actual underlying bucket
> -----------------------------------------------------------------------------
>
> Key: HDDS-11705
> URL: https://issues.apache.org/jira/browse/HDDS-11705
> Project: Apache Ozone
> Issue Type: Sub-task
> Affects Versions: 1.4.0
> Reporter: Swaminathan Balachandran
> Assignee: Swaminathan Balachandran
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.0.0
>
>
> Ozone snapshot uses /volume/bucket path as a key prefix to traverse the key
> space and generate snapshot diff. It also uses the same volume bucket path to
> maintain a snapshot chain for garbage collection. Currently, Ozone snapshot
> doesn’t resolve the linked bucket to the original bucket and creates a
> snapshot and performs other snapshot operations on the linked bucket.
> Since there is no key based on the linked volume bucket path in the original
> bucket, SnapDiff returns an empty diff (no diff).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
