Bug of 1.9.X Aws::Client::ClientConfiguration?

[RoyZhang2022]

Hi,

Today I found for Aws::Client::ClientConfiguration if I set max retry to 0, some AWS API which is using the ClientConfiguration could fail with error "AWS API ERROR: ThrottlingException: Request rate limit exceeded". Once I add a check to disallow max retry to be 0, there is no any problem. I have seen this problem on Windows 10 and Linux for SDK 1.9.220. I also verified same code with 1.10.55 and did not see any problem. So this should be a bug of 1.9.X which is fixed in 1.10.55? Please confirm if anyone knows about this. Thanks!

  Aws::Client::ClientConfiguration clientCfg;
  clientCfg.region = `us-west-2`;
  clientCfg.enableEndpointDiscovery = true;
  clientCfg.connectTimeoutMs = 3000;
  clientCfg.requestTimeoutMs = 10000;
  clientCfg.maxConnections = 25;

  // When GetMaxRetry() is 0, it could lead to error
  // "AWS API ERROR: ThrottlingException: Request rate limit exceeded"
  if (GetMaxRetry() > 0) {
    clientCfg.retryStrategy =
        std::make_shared< Aws::Client::DefaultRetryStrategy >(
            GetMaxRetry());
  }
  ......
 Aws::TimestreamQuery::TimestreamQueryClient(credentials, clientCfg);

Best,
Roy

[jmklix]

I'm not sure what caused this, but I'm glad that it's no longer a problem for you. Please let us know is you see this again in version 1.11+

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.