Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in Client-side rate limiting / Retries and Timeouts doc #2759

Merged
merged 1 commit into from
Aug 30, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/configuring-sdk/retries-timeouts.md
Original file line number Diff line number Diff line change
Expand Up @@ -144,8 +144,8 @@ than what's available results in operation failure with a

The default implementation is parameterized as follows (how to modify each setting):
- a capacity of 500 (set the value of RateLimiter on StandardOptions using [NewTokenRateLimit]({{< apiref "aws/ratelimit#NewTokenRateLimit" >}}))
- a retry caused by a timeout costs 10 tokens (set RetryCost on StandardOptions)
- a retry caused by other errors costs 5 tokens (set RetryTimeoutCost on StandardOptions)
- a retry caused by a timeout costs 10 tokens (set RetryTimeoutCost on StandardOptions)
- a retry caused by other errors costs 5 tokens (set RetryCost on StandardOptions)
- an operation that succeeds on the 1st attempt adds 1 token (set NoRetryIncrement on StandardOptions)
- operations that succeed on the 2nd or later attempt do not add back any tokens

Expand Down
Loading