[HDDS-2953] Handle replay of S3 requests

• 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: 28/Jan/20 18:28
• Updated: 04/Jun/20 20:17
• Resolved: 11/Feb/20 01:05

Description

To ensure that S3 operations is 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.

In this Jira, the following requests are made idempotent:

• S3InitiateMultipartUploadRequest
• S3MultipartUploadCommitPartRequest
• S3MultipartUploadCompleteRequest
• S3MultipartUploadAbortRequest

Issue Links

• links to: GitHub Pull Request #504