-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Aws retry settings are not working #3131
Comments
|
Hi @jmklix thanks for the response. Will retry strategy works for crt client? If yes can you please tell us how it actually works? |
Yes, retry strategy should work for the s3crt client. It was added recently in this PR: #3110. So please make sure that you are using the latest version of this sdk. You can check out the pr for details of how each option is supposed to work, but for if (strategyToUse == CrtRetryStrategyType::NO_RETRY)
{
aws_standard_retry_options options {};
options.initial_bucket_capacity = 1;
return aws_retry_strategy_new_standard(Aws::get_aws_allocator(), &options);
} And then that called this: /* standard default is 3. */
if (!config->backoff_retry_options.max_retries) {
config_cpy.max_retries = 3;
} So it looks like this might not be working correctly as I don't see max_retries get set for anything other then |
This should be fixed with this PR. Please update to the latest version on this sdk and let us know if you see any more unexpected behavior with the retry settings |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Can someone explain how this retry strategy works, i configured timeout configs to 100ms and retry strategy to NO_RETRY. But still i am seeing requests are not getting cancelled and time to get object is more than 1 second.
sample code snippet.
aws cpp SDK version : 1.11.408
Originally posted by @Manjunathagopi in #2594 (comment)
The text was updated successfully, but these errors were encountered: