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

["Jeff Widman (JIRA)" <ji...@apache.org>]

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

Jeff Widman commented on KAFKA-2019:
------------------------------------

As noted in KIP-54 (https://cwiki.apache.org/confluence/display/pages/viewpage.action?pageId=62692483) this is not relevant to the new consumer.

Could someone update the issue title to make it clear it only applies to the old consumer?

I also suspect this may never get merged as the new consumer is the future, in which case it'd be nice if this were closed as "wontfix"


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