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/28 18:29:00 UTC

[jira] [Created] (HDDS-2953) Handle replay of S3 requests

Hanisha Koneru created HDDS-2953:
------------------------------------

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


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



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