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 2020/01/30 00:01:00 UTC
[jira] [Updated] (HDDS-2894) Handle replay of KeyDelete and
KeyRename Requests
[ https://issues.apache.org/jira/browse/HDDS-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-2894:
---------------------------------
Labels: pull-request-available (was: )
> Handle replay of KeyDelete and KeyRename Requests
> -------------------------------------------------
>
> Key: HDDS-2894
> URL: https://issues.apache.org/jira/browse/HDDS-2894
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Labels: pull-request-available
>
> To ensure that key deletion and rename operations are idempotent, compare the transactionID with the objectID and updateID to make sure that the transaction is not a replay. If the transactionID <= updateID, then it implies that the transaction is a replay and hence it should be skipped.
> OMKeyDeleteRequest and OMKeyRenameRequest are made idempotent in this Jira.
--
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