Skip to content

chore(clients): add AWS retry customizations for DynamoDB, SQS, SFN, SWF - #7922

Merged
kuhe merged 1 commit into
mainfrom
kuhe/feat/retry2.1
Apr 7, 2026
Merged

kuhe merged 1 commit into
mainfrom
kuhe/feat/retry2.1

Conversation

@kuhe

@kuhe kuhe commented Apr 7, 2026 •

Copy link
Copy Markdown
Contributor

Issue

implements AWS portion of smithy-lang/smithy-typescript#1922
follows #7916

Description

  • new retry behavior is currently gated behind SMITHY_NEW_RETRIES_2026 process.env entry. It is read only once at start-up, so changing the value is not possible.
    • if enabled, DynamoDB and DynamoDB Streams will default to 4 maximum attempts per request instead of 3 (default for most clients).
    • DynamoDB family of clients will also retry slightly faster between attempts
    • For certain long polling operations like SQS ReceiveMessage that may run in a tight loop, the SDK will perform a backoff to prevent the loop from iterating too quickly in the event of a service outage.

You can read more about the upcoming retry behavior changes in smithy-lang/smithy-typescript#1922. The gist of it is that the behavior has been designed to give your requests the optimal chance of success and recovery speed in a variety of error scenarios.

Enabling SMITHY_NEW_RETRIES_2026 after process start

This is an internal API and may be removed in the future.

import { Retry } from "@smithy/util-retry";

Retry.v2026 = true;

Testing

new e2e/integration tests

Checklist

  • If the PR is a feature, add integration tests (*.integ.spec.ts) or E2E tests.
    • It's not a feature.
  • My E2E tests are resilient to concurrent i/o.
    • I didn't write any E2E tests.
  • I added access level annotations e.g. @public, @internal tags and enabled doc generation on the package. Remember that access level annotations go below the description, not above.
    • I didn't add any public functions.
  • Streams - how do they work?? My WebStream readers/locks are properly lifecycled. Node.js stream backpressure is handled. Error handling.
    • No streams here.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@kuhe
kuhe requested a review from a team as a code owner April 7, 2026 14:44
@kuhe
kuhe force-pushed the kuhe/feat/retry2.1 branch from 88fbaf0 to 07a9260 Compare April 7, 2026 15:40
@kuhe
kuhe force-pushed the kuhe/feat/retry2.1 branch from 07a9260 to 089f74c Compare April 7, 2026 15:40
@kuhe
kuhe merged commit 4d9c592 into main Apr 7, 2026
8 checks passed
@kuhe
kuhe deleted the kuhe/feat/retry2.1 branch April 7, 2026 17:02
@github-actions

Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Apr 22, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

⌂ 换网址