[
https://issues.apache.org/jira/browse/FLINK-29476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613350#comment-17613350
]
Danny Cranmer commented on FLINK-29476:
---------------------------------------
Merged commit
[{{49e0041}}|https://github.com/apache/flink/commit/49e0041042e65e0045701cc5514ce55d74796ba2]
into master
Merged commit
[{{19aa96a}}|https://github.com/apache/flink/commit/19aa96ac09e1518b3a761f8320681bc5e046f655]
into release-1.16
Merged commit
[{{9715b5e}}|https://github.com/apache/flink/commit/9715b5e641e76a33c0b869409ce5094f5727105a]
into release-1.15
> 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)
