[
https://issues.apache.org/jira/browse/KAFKA-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758711#comment-16758711
]
Matthias J. Sax commented on KAFKA-4133:
----------------------------------------
Feature freeze deadline for 2.2 was yesterday. Moving this 2.3 release.
> Provide a configuration to control consumer max in-flight fetches
> -----------------------------------------------------------------
>
> Key: KAFKA-4133
> URL: https://issues.apache.org/jira/browse/KAFKA-4133
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: Jason Gustafson
> Assignee: Mickael Maison
> Priority: Major
> Labels: kip
> Fix For: 2.2.0
>
>
> With KIP-74, we now have a good way to limit the size of fetch responses, but
> it may still be difficult for users to control overall memory since the
> consumer will send fetches in parallel to all the brokers which own
> partitions that it is subscribed to. To give users finer control, it might
> make sense to add a `max.in.flight.fetches` setting to limit the total number
> of concurrent fetches at any time. This would require a KIP since it's a new
> configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
