[HADOOP-19221] S3A: Unable to recover from failure of multipart block upload attempt "Status Code: 400; Error Code: RequestTimeout"

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.5.0, 3.4.1
• Component/s: fs/s3
• Labels: pull-request-available

Release Note

S3A upload operations can now recover from failures where the store returns a 500 error. There is an option to control whether or not the S3A client itself attempts to retry on a 50x error other than 503 throttling events (which are independently processed as before). Option: fs.s3a.retry.http.5xx.errors . Default: true

• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 08/Jul/24 15:57
• Updated: 03/Oct/24 10:45
• Resolved: 16/Sep/24 11:17

Description

If a multipart PUT request fails for some reason (e.g. networrk error) then all subsequent retry attempts fail with a 400 Response and ErrorCode RequestTimeout .

Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. (Service: Amazon S3; Status Code: 400; Error Code: RequestTimeout; Request ID:; S3 Extended Request ID:

The list of supporessed exceptions contains the root cause (the initial failure was a 500); all retries failed to upload properly from the source input stream RequestBody.fromInputStream(fileStream, size).

Hypothesis: the mark/reset stuff doesn't work for input streams. On the v1 sdk we would build a multipart block upload request passing in (file, offset, length), the way we are now doing this doesn't recover.

probably fixable by providing our own ContentStreamProvider implementations for

1. file + offset + length
2. bytebuffer
3. byte array

The sdk does have explicit support for the memory ones, but they copy the data blocks first. we don't want that as it would double the memory requirements of active blocks.

Issue Links

• contains: HADOOP-19245 S3ABlockOutputStream no longer sends progress events in close()
• links to: aws-sdk-java-v2/issues/5415
• links to: GitHub Pull Request #6938
• links to: GitHub Pull Request #7044