flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9691) Modify run loop in Kinesis ShardConsumer to not sleep for a fixed fetchIntervalMillis
Date Wed, 11 Jul 2018 17:45:00 GMT

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

Thomas Weise commented on FLINK-9691:
-------------------------------------

Should this be fixed in 1.4.x and 1.5.x also?

> Modify run loop in Kinesis ShardConsumer to not sleep for a fixed fetchIntervalMillis
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-9691
>                 URL: https://issues.apache.org/jira/browse/FLINK-9691
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kinesis Connector
>    Affects Versions: 1.5.0, 1.4.2
>            Reporter: Lakshmi Rao
>            Assignee: Jamie Grier
>            Priority: Major
>
> Currently the ShardConsumer in the Kinesis connector sleeps for a fixed [fetchIntervalMillis|https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/internals/ShardConsumer.java#L210] resulting
in the shard consumer sleeping for more time than necessary and not optimally reading from
Kinesis. It should only be sleeping for (fetchIntervalMillis - time taken to process records)
before making the subsequent getRecords call. 



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

Mime
View raw message