You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hemant Kumar (Jira)" <ji...@apache.org> on 2024/08/15 23:50:00 UTC
[jira] [Resolved] (HDDS-11137) Remove the locks from SnapshotPurge and SnapshotSetProperty APIs
[ https://issues.apache.org/jira/browse/HDDS-11137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemant Kumar resolved HDDS-11137.
---------------------------------
Fix Version/s: 1.5.0
Target Version/s: 1.5.0
Resolution: Fixed
> Remove the locks from SnapshotPurge and SnapshotSetProperty APIs
> ----------------------------------------------------------------
>
> Key: HDDS-11137
> URL: https://issues.apache.org/jira/browse/HDDS-11137
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: OM
> Reporter: Hemant Kumar
> Assignee: Hemant Kumar
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> In HDDS-10590, we introduce the locks to achieve synchronization among snapshot purge, set snapshot property, and SSTFilteringService because they are updating the snapshotInfo table and might be causing the snapshot chain corruption because SSTFilteringService doesn't go through Ratis.
> In HDDS-11068, we found that the snapshot chain corruption issue still exists even after the locks. And the actual reason is that SSTFilteringService directly updates the DB and persists it. More details in HDDS-11068.
> Once we move sstFiltered flag out of snapshotInfoTable, we need to revisit the need for locks. We might not need locks after that and just rely on applyTransaction which is single threaded.
--
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