You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/10/28 17:28:00 UTC

[jira] [Updated] (HDDS-13847) Introduce Snapshot Content Lock to lock table contents

     [ https://issues.apache.org/jira/browse/HDDS-13847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HDDS-13847:
----------------------------------
    Labels: pull-request-available  (was: )

> Introduce Snapshot Content Lock to lock table contents
> ------------------------------------------------------
>
>                 Key: HDDS-13847
>                 URL: https://issues.apache.org/jira/browse/HDDS-13847
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Swaminathan Balachandran
>            Assignee: Swaminathan Balachandran
>            Priority: Major
>              Labels: pull-request-available
>
> Introduce Snapshot Content Lock to prevent writes on a snapshot during snapshot defrag. Even though GC lock would be acquired during defrag on leader the contents in the snapshot is only guaranteed to be same for leader however defrag on follower can happen at any time, thus a lock should be acquired while the defrag to prevent the contents from changing in the snapshot which would mainly happen in 3 transactions during OM double buffer flush on followers i.e. 
> OMSnapshotMoveTableKeysResponse, OMKeyPurgeResponse, OMDirectoriesPurgeResponseWithFSO.



--
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