kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mickael Maison (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4133) Provide a configuration to control consumer max in-flight fetches
Date Tue, 20 Sep 2016 09:43:20 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15506187#comment-15506187

Mickael Maison commented on KAFKA-4133:

Due to a KIP # collision, it is now KIP-81: https://cwiki.apache.org/confluence/display/KAFKA/KIP-81%3A+Max+in-flight+fetches

> 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
> 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

View raw message