You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/12/30 05:23:58 UTC

[jira] [Updated] (KAFKA-2019) Old consumer RoundRobinAssignor clusters by consumer

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

Ewen Cheslack-Postava updated KAFKA-2019:
-----------------------------------------
    Summary: Old consumer RoundRobinAssignor clusters by consumer  (was: RoundRobinAssignor clusters by consumer)

> Old consumer RoundRobinAssignor clusters by consumer
> ----------------------------------------------------
>
>                 Key: KAFKA-2019
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2019
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>            Reporter: Joseph Holsten
>            Assignee: Neha Narkhede
>            Priority: Minor
>         Attachments: 0001-sort-consumer-thread-ids-by-hashcode.patch, KAFKA-2019.patch
>
>
> When rolling out a change today, I noticed that some of my consumers are "greedy", taking far more partitions than others.
> The cause is that the RoundRobinAssignor is using a list of ConsumerThreadIds sorted by toString, which is {{ "%s-%d".format(consumer, threadId)}}. This causes each consumer's threads to be adjacent to each other.
> One possible fix would be to define ConsumerThreadId.hashCode, and sort by that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)