Upgrade to aws-sdk-sqs="1.23.0" causing timeouts
#1148
Comments
Smotrov
added
bug
aajtodd
added
p1
|
FWIW after merging rust-lang/crates.io#8610 we noticed similar issues on the crates.io staging environment:
|
…-sdk-rust-monorepo" This reverts commit 34bd67e, reversing changes made to b6b4386. see awslabs/aws-sdk-rust#1148
…-monorepo" (#8640) This reverts commit 34bd67e, reversing changes made to b6b4386. see awslabs/aws-sdk-rust#1148
Smotrov
changed the title
aws-sdk-sqs = "1.23.0" causing timeoutsaws-sdk-sqs="1.23.0" causing timeouts
|
Thanks for the issue, we are looking into this now and how best to address it. As a workaround you can disable let config = aws_config::defaults(aws_config::BehaviorVersion::latest())
.stalled_stream_protection(
StalledStreamProtectionConfig::enabled()
.upload_enabled(false)
.build(),
)
.load()
.await;This will keep stalled stream protection for downloads enabled and only disable uploads (which was the default prior to let config = aws_config::defaults(aws_config::BehaviorVersion::latest())
.stalled_stream_protection(StalledStreamProtectionConfig::disabled())
.load()
.await; |
|
Explicitly setting a deprecated behavior version fixes this as well:
|
…lete (#3644) ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here --> * awslabs/aws-sdk-rust#1141 * awslabs/aws-sdk-rust#1146 * awslabs/aws-sdk-rust#1148 ## Description * Disables stalled stream upload protection for requests with an empty/zero length body. * Disables stalled stream upload throughput checking once the request body has been read and handed off to the HTTP layer. ## Testing Additional integration tests added covering empty bodies and completed uploads. Tested SQS issue against latest runtime and can see it works now. The S3 `CopyObject` issue is related to downloads and will need a different solution. ## Checklist <!--- If a checkbox below is not applicable, then please DELETE it rather than leaving it unchecked --> - [x] I have updated `CHANGELOG.next.toml` if I made changes to the smithy-rs codegen or runtime crates - [x] I have updated `CHANGELOG.next.toml` if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._ --------- Co-authored-by: Zelda Hessler <zhessler@amazon.com> Co-authored-by: ysaito1001 <awsaito@amazon.com>
|
It seams like the fix is already merged into |
|
We just released the runtime crate updates: https://github.com/smithy-lang/smithy-rs/releases/tag/release-2024-05-21 |
|
New release brought new errors. Unfortunately unable so far... |
|
I'm looking into a fix right now. Hopefully we can get it out this week. |
|
@Smotrov, We have just released a new version in the smithy-rs repository. Curious to know whether the issue can be resolved if you use |
|
Comments on closed issues are hard for our team to see. |
Describe the bug
After updating to
aws-sdk-sqs = "1.23.0"facing massive timeouts in the log.Expected Behavior
Would be good if there will be no timeouts.
Current Behavior
Vast majority of calls to SQS are time outed with following error
Reproduction Steps
Upgrade to
aws-sdk-sqs = "1.23.0"Try to work with AWS SQS
Possible Solution
No response
Additional Information/Context
aws-sdk-sqs = "1.24.0"does not solving the bugVersion
The text was updated successfully, but these errors were encountered: