[
https://issues.apache.org/jira/browse/FLINK-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16567647#comment-16567647
]
ASF GitHub Bot commented on FLINK-10020:
----------------------------------------
tweise opened a new pull request #6482: [FLINK-10020] [kinesis] Support
recoverable exceptions in listShards.
URL: https://github.com/apache/flink/pull/6482
This change fixes the retry behavior of listShards to match what getRecords
already supports. Importantly this will prevent the subtask from failing on
transient listShards errors that we can identify based on well known
exceptions. These are recoverable and should not lead to unnecessary recovery
cycles that cause downtime.
R: @glaksh100 @jgrier @tzulitai
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Kinesis Consumer listShards should support more recoverable exceptions
> ----------------------------------------------------------------------
>
> Key: FLINK-10020
> URL: https://issues.apache.org/jira/browse/FLINK-10020
> Project: Flink
> Issue Type: Improvement
> Components: Kinesis Connector
> Reporter: Thomas Weise
> Assignee: Thomas Weise
> Priority: Major
> Labels: pull-request-available
>
> Currently transient errors in listShards make the consumer fail and cause the
> entire job to reset. That is unnecessary for certain exceptions (like status
> 503 errors). It should be possible to control the exceptions that qualify for
> retry, similar to getRecords/isRecoverableSdkClientException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
