[
https://issues.apache.org/jira/browse/HDDS-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham resolved HDDS-2893.
--------------------------------------
Fix Version/s: 0.5.0
Resolution: Fixed
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
