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

Posted to dev@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2016/06/04 02:59:59 UTC

[jira] [Created] (FLINK-4018) Configurable idle time between getRecords requests to Kinesis shards

Tzu-Li (Gordon) Tai created FLINK-4018:
------------------------------------------

             Summary: Configurable idle time between getRecords requests to Kinesis shards
                 Key: FLINK-4018
                 URL: https://issues.apache.org/jira/browse/FLINK-4018
             Project: Flink
          Issue Type: Sub-task
          Components: Streaming Connectors
    Affects Versions: 1.1.0
            Reporter: Tzu-Li (Gordon) Tai
            Assignee: Tzu-Li (Gordon) Tai


Currently, the Kinesis consumer is calling getRecords() right after finishing previous calls. This results in easily reaching Amazon's limitation of 5 GET requests per shard per second. Although the code already has backoff & retry mechanism, this will affect other applications consuming from the same Kinesis stream.

Along with this new configuration and the already existing `KinesisConfigConstants.CONFIG_SHARD_RECORDS_PER_GET`, users will have more control on the desired throughput behaviour for the Kinesis consumer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)