[jira] [Resolved] (HDDS-2970) Add Tombstone Marker to Ozone Objects to avoid all replays

["Arpit Agarwal (Jira)" <ji...@apache.org>]

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

Arpit Agarwal resolved HDDS-2970.
---------------------------------
    Resolution: Done

This should be handled correctly after recent changes to OM replay logic.

> Add Tombstone Marker to Ozone Objects to avoid all replays
> ----------------------------------------------------------
>
>                 Key: HDDS-2970
>                 URL: https://issues.apache.org/jira/browse/HDDS-2970
>             Project: Hadoop Distributed Data Store
>          Issue Type: New Feature
>          Components: om
>            Reporter: Hanisha Koneru
>            Priority: Major
>
> When ratis is enabled for OM, it is possible that transactions will be replayed. Though most of the replays would be caught and ignored, there are some scenarios in which a transaction could be replayed.
> For example, Key1 is created and deleted. If Key1 create transaction is replayed, there is no way to determine if this is a replayed transaction as Key1 would not be existing in the DB anymore. 
> To avoid such replay scenarios, we could add something similar to HBase's Tombstone marker to entries when they are deleted. A background job can later delete these objects (once a snapshot is taken with snapshot index greater than the object's updateID).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org