[jira] [Updated] (FLINK-33260) Custom Error Handling for Kinesis EFO Consumer

["Danny Cranmer (Jira)" <ji...@apache.org>]

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

Danny Cranmer updated FLINK-33260:
----------------------------------
    Summary: Custom Error Handling for Kinesis EFO Consumer  (was: Custom Error Handling for Kinesis Consumer)

> Custom Error Handling for Kinesis EFO Consumer
> ----------------------------------------------
>
>                 Key: FLINK-33260
>                 URL: https://issues.apache.org/jira/browse/FLINK-33260
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kinesis
>    Affects Versions: aws-connector-4.2.0
>            Reporter: Danny Cranmer
>            Assignee: Emre Kartoglu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: aws-connector-4.3.0
>
>
> Background
> The Kinesis Consumer exposes various configuration that allows the user to define retry and backoff strategies when dealing with errors. However, the configuration does not allow the user to configure which errors are retryable, or different strategies for different errors. The error handling logic is hard coded within the connector. Over time we discover errors that should be retryable that are not, for example KDS throwing 500 on SubscribeToShare or transient DNS issues. When these arise the user can either fork-fix the connector or log an issue and wait for the next version.
> h3. Scope
> Add the ability for the user to define retry/backoff strategy per error. This could be achieved using flexible configuration keys, or allowing the user to register their own retry strategies on the connector
>  



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