[
https://issues.apache.org/jira/browse/FLINK-36412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hong Liang Teoh updated FLINK-36412:
------------------------------------
Fix Version/s: aws-connector-5.0.0
> Retry strategies on Kinesis Sink
> --------------------------------
>
> Key: FLINK-36412
> URL: https://issues.apache.org/jira/browse/FLINK-36412
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / AWS, Connectors / Kinesis
> Affects Versions: aws-connector-4.3.0
> Reporter: Ed Berezitsky
> Priority: Major
> Fix For: aws-connector-4.4.0, aws-connector-5.0.0
>
>
> In case of internal Kinesis issues, Kinesis Sink connector crashes and causes
> application to stop
> {{java.util.concurrent.CompletionException:
> org.apache.flink.kinesis.shaded.software.amazon.awssdk.core.exception.SdkClientException:
> Unable to execute HTTP request: connection timed
> out:<ACCOUNT_ID>.data-kinesis.us-west-2.amazonaws.com/<10.x.x.x>:443 at
> org.apache.flink.kinesis.shaded.software.amazon.awssdk.utils.CompletableFutureUtils.errorAsCompletionException(CompletableFutureUtils.java:65)
> at
> org.apache.flink.kinesis.shaded.software.amazon.awssdk.core.internal.http.pipeline.stages.AsyncExecutionFailureExceptionReportingStage.lambda$execute$0(AsyncExecutionFailureExceptionReportingStage.java:51)}}
>
> The connector could introduce improved exception/error managing mechanism to
> allow an application to wait until connection is restored, controlled by
> additional parameters available for a users of the connector to set in a
> Flink aopp
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
