You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/07/28 21:59:00 UTC

[jira] [Updated] (KAFKA-4133) Provide a configuration to control consumer max in-flight fetches

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

Guozhang Wang updated KAFKA-4133:
---------------------------------
    Fix Version/s: 1.0.0

> 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
>             Fix For: 1.0.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
(v6.4.14#64029)