Call the AbortMultipartUpload function and call the RetryUpload progress bar problem

[xiaonaiquan]

I use TransferManager to upload files in segments,Then I called AbortMultipartUpload to abort the upload，Then I called AbortMultipartUpload to abort the upload, and when the upload status is ABORTED, I called RetryUpload to continue the upload, but this operation is not to continue the upload, but to upload again. Is this correct?I want to interrupt the upload and then continue. What should I do in this case?

[jmklix]

I don't think you want to be calling AbortMultiPartUpload, because as noted in the API docs:

By default, multi-part uploads will remain in a FAILED state if they fail, or a CANCELED state if they were canceled. Leaving failed uploads around still costs the owner of the bucket money. If you know you will not be retrying the request, abort the request after canceling it or if it fails and you don't intend to retry it.

So you only want to call abort if you have no intention of retrying the request. If the TransferStatus is in the failed state, that is when you want to call RetryUpload.

[xiaonaiquan]

@jmklix I actually restart the program after it exits and call RetryUpload, but RetryUpload seems to be uploading files from scratch.When I exit the program, I get the failed and successful ones from TransManager, and I save the failed ones locally.

[jmklix]

You can't resume or retry the upload after stopping your program. As I mentioned here it isn't possible with this version of the sdk. Because the SDK does not save the token(JSON) of the current progress locally. It is still in memory, so when you restart the program all progress is lost.

[xiaonaiquan]

@jmklix Thank you, I solved the problem, I saved the token(JSON) of the current progress locally and then restored it.

[jmklix]

I'm glad that you were able to solve this!

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.