[jira] [Comment Edited] (FLINK-39137) Add configurable delay between non-empty GetRecords calls in Kinesis source

["Andreas Bube (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-39137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105237#comment-18105237 ] 

Andreas Bube edited comment on FLINK-39137 at 8/19/26 10:37 AM:
----------------------------------------------------------------

[~jingjia88]. I've posted the PR now: [https://github.com/apache/flink-connector-aws/pull/254]. Since you've run into this issue yourself, I'd greatly appreciate it if you had a look and shared any comments.


was (Author: JIRAUSER310157):
[~jingjia88]. I've posted the PR now: [https://github.com/apache/flink-connector-aws/pull/254.] Since you've run into this issue yourself, I'd greatly appreciate it if you had a look and shared any comments.

> Add configurable delay between non-empty GetRecords calls in Kinesis source
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-39137
>                 URL: https://issues.apache.org/jira/browse/FLINK-39137
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / AWS
>    Affects Versions: 1.20.3, 2.2.0, 2.1.1, 2.3.0
>            Reporter: Andreas Bube
>            Priority: Minor
>              Labels: pull-request-available
>
> Kinesis {{GetRecords}} quota is easy to exhaust (5 calls/sec/shard limit). With multiple consumers on the same stream/shard, one eager reader can starve others.
> *Proposed change:* Add a new Kinesis Streams source config option to throttle polling after successful (non-empty) fetches:
>  * {{source.reader.nonempty-records-fetch-interval}}
>  ** {{Duration type}}
>  ** Zero by default (preserves current behavior)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)