[
https://issues.apache.org/jira/browse/FLINK-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442265#comment-16442265
]
ASF GitHub Bot commented on FLINK-9124:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/5803
As discussed on the mailing list
(http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Kinesis-getRecords-read-timeout-and-retry-td21844.html),
lets merge the PR as it is for now.
Some final remarks:
- I see that we already have a JIRA to improve generic configuration
support: https://issues.apache.org/jira/browse/FLINK-9188.
- For the fullJitterBackoff and retry handling, I wonder if a user-provided
retry handler would be more appropriate (as a future improvement). For example,
our Elasticsearch connector has something similar.
Merging this for 1.6.0 and 1.5.0 ..
> Allow customization of KinesisProxy.getRecords read timeout and retry
> ---------------------------------------------------------------------
>
> Key: FLINK-9124
> URL: https://issues.apache.org/jira/browse/FLINK-9124
> Project: Flink
> Issue Type: Task
> Components: Kinesis Connector
> Affects Versions: 1.4.2
> Reporter: Thomas Weise
> Assignee: Thomas Weise
> Priority: Minor
>
> It should be possible to change the socket read timeout and all other
> configuration parameters of the underlying AWS ClientConfiguration and also
> have the option to retry after a socket timeout exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
