[jira] [Updated] (FLINK-37841) Having adaptive retry strategy causing issues in DDB Connector

["Hong Liang Teoh (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-37841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hong Liang Teoh updated FLINK-37841:
------------------------------------
    Fix Version/s: aws-connector-5.2.0
                       (was: aws-connector-5.1.0)

> Having adaptive retry strategy causing issues in DDB Connector
> --------------------------------------------------------------
>
>                 Key: FLINK-37841
>                 URL: https://issues.apache.org/jira/browse/FLINK-37841
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / DynamoDB
>            Reporter: Abhi Gupta
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: aws-connector-5.2.0
>
>
> AWS docs say the following:
> > The adaptive retry strategy includes all the features of the standard strategy and adds a client-side rate limiter that measures the rate of throttled requests compared to non-throttled requests. The strategy uses this measurement to slow down the requests in an attempt to stay within a safe bandwidth, ideally causing zero throttling errors.
>  
> This means requests maybe getting slowed down and the connector not achieving desired performance in things like shard discovery. Having standard retry strategy should be able to better fix this issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)