[
https://issues.apache.org/jira/browse/HDDS-17659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18137785#comment-18137785
]
Andy Huang commented on HDDS-17659:
-----------------------------------
Verified against AWS S3 in ap-northeast-1 using AWS CLI. Sending the same
CompleteMultipartUpload request twice with the same bucket, key, upload ID, and
parts list succeeded both times (exit code 0). The second response body
contained CompleteMultipartUploadResult with the same ETag, rather than an
embedded Error.
> CompleteMultipartUpload returns 200 on AWS S3 but fails on Ozone
> ----------------------------------------------------------------
>
> Key: HDDS-17659
> URL: https://issues.apache.org/jira/browse/HDDS-17659
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: S3
> Reporter: Chung-En Lee
> Assignee: Andy Huang
> Priority: Major
>
> Sending the same CompleteMultipartUpload request again after it succeeded
> returns 200 on AWS S3 but 404 NoSuchUpload on Ozone.
> Steps to reproduce:
> # Create a multipart upload and upload part 1.
> # Send CompleteMultipartUpload.
> # Send the same CompleteMultipartUpload request again.
> Actual: Step 3 returns 404 NoSuchUpload.
> Expected: Step 3 returns 200, as on AWS S3.
> This can affect client retries. If the response to step 2 is lost, the AWS
> SDK for Java v2 retries by default, and the application gets
> NoSuchUploadException even though the object was created.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
