max backoff time per Operation

[michaetto]

Describe the feature

right now only initial backoff is configurable in shared or service configs, is it ?

Use Case

• when some complex async request is processed, sometimes it is desired to make sure sum of time of all async operations within (sequential and concurrent) do not not exceed some time limit
• implementing kind of circuit breaker retry pattern (using config retries wrapped up in custom retry mechanism)

Proposed Solution

• add configurable max backoff time per Operation
• also implementing circuit breaker retry pattern (as retry mode) in sdk would be great

Other Information

sdk version 0.52

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

A note for the community

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue, please leave a comment

[rcoh]

you can use https://docs.rs/aws-config/0.52.0/aws_config/timeout/struct.TimeoutConfig.html#method.operation_timeout which can be set either globally or on an individual service client.

Setting timeouts on an individual operation would be useful! I've created smithy-rs#2160 to track.

As a workaround, you can create a client with the specified backoff and use that for the operations in question

[aajtodd]

This has been possible for a while now via customize() to override config on a per/operation level and is documented in the developer guide. Closing.

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.