[
https://issues.apache.org/jira/browse/HDDS-11453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-11453:
----------------------------------
Labels: pull-request-available (was: )
> OmSnapshotPurge should be in a different ozone manager double buffer batch
> --------------------------------------------------------------------------
>
> Key: HDDS-11453
> URL: https://issues.apache.org/jira/browse/HDDS-11453
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Swaminathan Balachandran
> Assignee: Swaminathan Balachandran
> Priority: Major
> Labels: pull-request-available
>
> Since purgeSnapshot transaction on a standalone basis is an idempotent
> operation. Once the directory gets deleted the previous transactions that
> have been performed on the snapshotted rocksdb would start failing on replay
> since those transactions have not been committed but the directory could
> have been partially deleted/ fully deleted. This could also lead to
> inconsistencies in the DB reads from the purged rocksdb if operations are
> not performed consciously.
> Creating a separate rocksdb batch in ozone manager double buffer will ensure
> all transactions before have been flushed to the disk before purging the
> rocksdb, ensuring the previous ratis transactions will never get replayed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
