NoSuchUpload: The specified upload does not exist #450
Milestone
Comments
igungor
pushed a commit
that referenced
this issue
Aug 2, 2022
With this change, doUpload method will retry the multipart upload on NoSuchUploadError if the no-such-upload-retry-count flag is used with cp or sync and the value of the special metadata in remote file does not match the one placed in upload request (or does not exists at all) . Otherwise (if it is different), it will assume that upload was successful and ignore the error. Retry logic is placed into s3.Put since it is possible to restart upload operation and write unit test there. For the retry condition, it will use a user defined metadata field. If the no-such-upload-retry-count given (with positive parameter), then it will put a random string as a user defined metadata. Then, upon the s3.NoSuchUpload error, it will check if that field matches with the one placed or not. If it does not match (or does not even exists), then the upload will be retried. Fixes #450
Repository owner
moved this from In Progress
to Done
in s5cmd
Aug 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently we started to see the error below , couldn't find anything that retries on this case. It basically fails after getting this error.
ERROR \"cp data s3://data": MultipartUpload: upload multipart failed upload id: IDXXXXXXXXXX caused by: NoSuchUpload: The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. status code: 404, request id: PJXXXXX, host id: HOSTIDXXThe text was updated successfully, but these errors were encountered: