[HDDS-2893] Handle replay of KeyPurge Request

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Component/s: OM HA, Ozone Manager
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Hanisha Koneru
• Reporter: Hanisha Koneru
• Created: 15/Jan/20 23:02
• Updated: 04/Jun/20 20:16
• Resolved: 01/Feb/20 00:49

Description

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.

Issue Links

• links to: GitHub Pull Request #450