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

Posted to dev@kafka.apache.org by "Boyang Chen (JIRA)" <ji...@apache.org> on 2018/03/28 03:25:00 UTC

[jira] [Created] (KAFKA-6723) Separate "max.poll.record" for restore consumer and common consumer

Boyang Chen created KAFKA-6723:
----------------------------------

             Summary: Separate "max.poll.record" for restore consumer and common consumer
                 Key: KAFKA-6723
                 URL: https://issues.apache.org/jira/browse/KAFKA-6723
             Project: Kafka
          Issue Type: Improvement
          Components: streams
            Reporter: Boyang Chen
            Assignee: Boyang Chen


Currently, Kafka Streams use `max.poll.record` config for both restore consumer and normal stream consumer. In reality, they are doing different processing workloads, and in order to speed up the restore speed, restore consumer is supposed to have a higher throughput by setting `max.poll.record` higher. The change involved is trivial: [https://github.com/abbccdda/kafka/commit/cace25b74f31c8da79e93b514bcf1ed3ea9a7149]

However, this is still a public API change (introducing a new config name), so we need a KIP.



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