You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Lakshmi Rao (JIRA)" <ji...@apache.org> on 2018/07/24 19:56:00 UTC

[jira] [Assigned] (FLINK-9897) Further enhance adaptiveReads in Kinesis Connector to read more records in the case of long running loops

     [ https://issues.apache.org/jira/browse/FLINK-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lakshmi Rao reassigned FLINK-9897:
----------------------------------

    Assignee: Lakshmi Rao

> Further enhance adaptiveReads in Kinesis Connector to read more records in the case of long running loops
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-9897
>                 URL: https://issues.apache.org/jira/browse/FLINK-9897
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kinesis Connector
>            Reporter: Lakshmi Rao
>            Assignee: Lakshmi Rao
>            Priority: Major
>              Labels: pull-request-available
>
> In FLINK-9692, we introduced the ability for the shardConsumer to adaptively read more records based on the current average record size to optimize the 2 Mb/sec shard limit. The feature maximizes  maxNumberOfRecordsPerFetch of 5 reads/sec (as prescribed by Kinesis limits). In the case where applications take more time to process records in the run loop, they are no longer able to read at a frequency of 5 reads/sec (even though their fetchIntervalMillis maybe set to 200 ms). In such a scenario, the maxNumberOfRecordsPerFetch should be calculated based on the time that the run loop actually takes as opposed to fetchIntervalMillis. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)