[
https://issues.apache.org/jira/browse/HDDS-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-13035:
------------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Snapshot Deleting Service should hold write locks while purging deleted
> snapshots
> ---------------------------------------------------------------------------------
>
> Key: HDDS-13035
> URL: https://issues.apache.org/jira/browse/HDDS-13035
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Swaminathan Balachandran
> Assignee: Swaminathan Balachandran
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.1.0
>
>
> Currently SnapshotDeletingService waits for KeyDeletingService &
> DirectoryDeletingService to finish before it starts to move entries from the
> deleted snapshot to the next snapshot in the chain. With ReclaimableFilter
> implementation both KeyDeletingService & DirectoryDeletingService are going
> to hold read locks on the previous snapshot in the chain. Now before
> processing a deleted snapshot the snapshot deleting service can just acquire
> write locks on the deleted snapshot and next snapshot in the chain which
> would prevent any parallel instance of KeyDeletingService or
> DirectoryDeletingService running on an inconsistent state of the snapshot.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
