[jira] [Updated] (FLINK-9691) Modify run loop in Kinesis ShardConsumer to not sleep for a fixed fetchIntervalMillis
[ https://issues.apache.org/jira/browse/FLINK-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated FLINK-9691: Fix Version/s: (was: 1.5.3) 1.5.2 > 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 > Fix For: 1.5.2, 1.6.0 > > > 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)
[jira] [Updated] (FLINK-9691) Modify run loop in Kinesis ShardConsumer to not sleep for a fixed fetchIntervalMillis
[ https://issues.apache.org/jira/browse/FLINK-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated FLINK-9691: Fix Version/s: (was: 1.6.1) (was: 1.7.0) 1.6.0 > 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 > Fix For: 1.5.3, 1.6.0 > > > 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)
[jira] [Updated] (FLINK-9691) Modify run loop in Kinesis ShardConsumer to not sleep for a fixed fetchIntervalMillis
[ https://issues.apache.org/jira/browse/FLINK-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Rohrmann updated FLINK-9691: - Fix Version/s: (was: 1.6.0) 1.7.0 1.6.1 > 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 > Fix For: 1.5.3, 1.6.1, 1.7.0 > > > 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)
[jira] [Updated] (FLINK-9691) Modify run loop in Kinesis ShardConsumer to not sleep for a fixed fetchIntervalMillis
[ https://issues.apache.org/jira/browse/FLINK-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated FLINK-9691: Fix Version/s: 1.6.0 1.5.2 > 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 > Fix For: 1.5.2, 1.6.0 > > > 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)
[jira] [Updated] (FLINK-9691) Modify run loop in Kinesis ShardConsumer to not sleep for a fixed fetchIntervalMillis
[ https://issues.apache.org/jira/browse/FLINK-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jamie Grier updated FLINK-9691: --- Affects Version/s: 1.5.0 1.4.2 > 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)
