You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Todd Palino (JIRA)" <ji...@apache.org> on 2017/04/12 00:32:41 UTC
[jira] [Updated] (KAFKA-5056) Shuffling of partitions in old
consumer fetch requests removed
[ https://issues.apache.org/jira/browse/KAFKA-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Palino updated KAFKA-5056:
-------------------------------
Summary: Shuffling of partitions in old consumer fetch requests removed (was: Shuffling of partitions in old consume fetch requests removed)
> Shuffling of partitions in old consumer fetch requests removed
> --------------------------------------------------------------
>
> Key: KAFKA-5056
> URL: https://issues.apache.org/jira/browse/KAFKA-5056
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.1.0
> Reporter: Todd Palino
> Assignee: Todd Palino
>
> [KIP-74|https://cwiki.apache.org/confluence/display/KAFKA/KIP-74%3A+Add+Fetch+Response+Size+Limit+in+Bytes] deprecated the constructor to {{FetchRequest}} which shuffles the {{requestInfo}} parameter, in favor of round robin reordering logic added to the replica fetcher and the consumer API. However, this was not added to the old consumer {{ConsumerFetcherThread}}, which has resulted in unfair partition fetching since 0.10.1.
> In order to maintain the old consumer, we need to add the removed shuffle to {{buildFetchRequest}} as the topic-partition list for each {{FetchRequest}} is composed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)