Skip to content

Retry Wasabi TemporarilyUnavailable S3 errors - #3952

Closed
apeschar wants to merge 2 commits into
aws:mainfrom
apeschar:fix/wasabi-temporarily-unavailable-aws
Closed

apeschar wants to merge 2 commits into
aws:mainfrom
apeschar:fix/wasabi-temporarily-unavailable-aws

Conversation

@apeschar

Copy link
Copy Markdown

Wasabi returns TemporarilyUnavailable for transient storage failures. The XML marshaller treats this unknown name as non-retryable, even on HTTP 503, aborting multipart uploads instead of retrying the affected part.

Map it to retryable SERVICE_UNAVAILABLE, with regression tests for XML classification and unchanged unknown/NoSuchKey behavior.

Reproduced using ClickHouse 26.9.4.3 and loopback mock S3: identical 503 responses fail after one part attempt with TemporarilyUnavailable, but retry successfully with ServiceUnavailable.

Draft: SDK unit tests/build verification pending. Also proposed in ClickHouse#41. This changes generated code; guidance on the preferred non-generated compatibility hook is welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant