Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

If an upload fails, pbm retry mechanism is using the same upload id and fails.

Description

When a chunk is getting uploaded and if it fails in the middle, the retry mechanism from pbm with same upload id is not accepting in the next retry causing backup failure.

 

For example - Chunk with 50 gb data with upload id 1234 is getting uploaded and in the middle like if 25 gb gets uploaded and then failed. PBM retries with sample upload id 1234 an current S3 storage is not accepting the same upload id as part of incomplete chunk that is with 25 gb data is already available in the current storage.

Environment

None

AFFECTED CS IDs

CS0041577

Attachments

6

Activity

Show:

Jan Mynar March 28, 2024 at 1:03 PM

see the comment

Oleksandr Havryliak November 8, 2023 at 9:20 AM

Hi !

Unfortunately we can not reproduce this issue, but I can suggest to upgrade PBM to the latest version. The reason is simple - newer version of PBM contains newer version of aws-sdk which can contain fixes like https://github.com/aws/aws-sdk-go/blob/main/CHANGELOG.md#sdk-bugs-7

PBM version 2.0.5 contains aws-sdk v1.44.159

PBM version 2.3.0 contains aws-sdk v1.44.312

IMO we should include sdk updates to our release notes, what do you think?

Cannot Reproduce

Details

Assignee

Reporter

Needs QA

Yes

Affects versions

Priority

Smart Checklist

Created November 2, 2023 at 4:58 PM
Updated March 28, 2024 at 1:03 PM
Resolved March 28, 2024 at 1:03 PM