I/O upload fails with “We encountered an internal error. Please try again”.

Description

While the object upload is in progress, there could be an error if there is CES IP movement, which might took longer time than expected.

The following error might be seen during the object upload.

Error

# s3user8401 cp /root/file_50G s3://newbucket-8401

warnings upload failed: ./file_50G to s3://newbucket-8401/file_50G An error occurred 
(InternalError) when calling the UploadPart operation (reached max retries: 2): We encountered an internal error. Please try again.

Workaround

Rerun the I/O upload from the client node, if this error occurs (the number of retries is based on the AWS_MAX_ATTEMPTS value set). Refer the AWS CLI documentation for the same.

Note: In case of I/O abort, the S3 user account can clean the disk space used by the partially uploaded object by using the following command.

System administrator can run a clean-up script on all the S3 users buckets, to check whether there are any left overs in the bucket directory where multipart-upload has failed. However, the recommendation is that the S3 user can clean up the failed uploads by using the S3 APIs.