You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Randall Hauch (Jira)" <ji...@apache.org> on 2019/10/15 16:11:00 UTC

[jira] [Resolved] (KAFKA-5828) Allow explicitly setting polling interval for Kafka connectors

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

Randall Hauch resolved KAFKA-5828.
----------------------------------
    Resolution: Won't Fix

Use quotas instead.

> Allow explicitly setting polling interval for Kafka connectors
> --------------------------------------------------------------
>
>                 Key: KAFKA-5828
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5828
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>            Reporter: Behrang Saeedzadeh
>            Priority: Major
>
> I have a Kafka cluster deployed in our internal data center and a Kafka Connect server deployed in AWS that gets data records from a topic on the Kafka cluster and writes them into a Kinesis stream.
> We want to ensure that our Kafka connect server does not saturate the available bandwidth between our internal data center and AWS.
> Using {{max.partition.fetch.bytes}} we can limit the upper bound of data that can be fetched in each poll call. If we can also configure the poll interval, then we can limit how much data is transferred per partition per second.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)