[
https://issues.apache.org/jira/browse/HDDS-9164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759158#comment-17759158
]
Ethan Rose commented on HDDS-9164:
----------------------------------
I've attached a sketch of OM Key commit flow with hsync to the parent jira
[here|https://issues.apache.org/jira/secure/attachment/13062461/hsync_block_commit_flow-Page-2.drawio.png].
If this flow makes sense if may be useful in implementing this jira. Note that
it assumes the lease implementation which has not been completed yet.
> [Hsync] moves blocks to deleted table on final commit
> -----------------------------------------------------
>
> Key: HDDS-9164
> URL: https://issues.apache.org/jira/browse/HDDS-9164
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Major
> Labels: pull-request-available
>
> As referred by HDDS-9146, having potential dataloss, a protective mechanism
> is handled to avoid deletion of blocks.
> Need to fix the problem by avoiding deletion of blocks and other impact on
> final commit.
> * For final commit, if request do not have Hsync, then based on hsync flag
> in om metadata, need treat as hsync feature and avoid treating as over-ride
> of blocks.
> * Same needs handle in cleanup of auto-cleanup of open files for hsync
> feature.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
