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

Posted to issues@ozone.apache.org by "Hanisha Koneru (Jira)" <ji...@apache.org> on 2020/01/15 23:03:00 UTC

[jira] [Created] (HDDS-2893) Handle replay of KeyPurge Request

Hanisha Koneru created HDDS-2893:
------------------------------------

             Summary: Handle replay of KeyPurge Request
                 Key: HDDS-2893
                 URL: https://issues.apache.org/jira/browse/HDDS-2893
             Project: Hadoop Distributed Data Store
          Issue Type: Sub-task
            Reporter: Hanisha Koneru
            Assignee: Hanisha Koneru


If KeyPurgeRequest is replayed, we do not want to purge the keys which were created after the original purge request was received. This could happen if a key was deleted, purged and then created and deleted again. The the purge request was replayed, it would purge the key deleted after the original purge request was completed.
Hence, to maintain idempotence, we should only purge those keys from DeletedKeys table that have updateID < transactionLogIndex of the request.




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