You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Danny Cranmer (Jira)" <ji...@apache.org> on 2022/10/06 07:44:00 UTC
[jira] [Resolved] (FLINK-29476) Kinesis Connector retry mechanism not applied to EOFException
[ https://issues.apache.org/jira/browse/FLINK-29476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Cranmer resolved FLINK-29476.
-----------------------------------
Resolution: Fixed
> Kinesis Connector retry mechanism not applied to EOFException
> -------------------------------------------------------------
>
> Key: FLINK-29476
> URL: https://issues.apache.org/jira/browse/FLINK-29476
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Affects Versions: 1.15.2
> Reporter: Alexander Fedulov
> Assignee: Alexander Fedulov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0, 1.15.3, 1.16.1
>
> Attachments: kinesis-exception.log
>
>
> The current retry mechanism in Kinesis connector only considers _SocketTimeoutException_ as recoverable: [KinesisProxy.java#L422|https://github.com/apache/flink/blob/release-1.16.0-rc1/flink-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/proxy/KinesisProxy.java#L422] , however we observed that communication can also fail with EOFException: [^kinesis-exception.log]
> This exception should also be considered recoverable and retried.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)