[HDDS-2956] Handle Replay of AllocateBlock 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: 30/Jan/20 00:08
• Updated: 04/Jun/20 20:17
• Resolved: 31/Jan/20 23:04

Description

To ensure that allocate block 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.

OMAllocateBlockRequest is made idempotent in this Jira.

Issue Links

• links to: GitHub Pull Request #505