[jira] [Updated] (KAFKA-564) Wildcard-based topic consumption should assign partitions to threads uniformly
[ https://issues.apache.org/jira/browse/KAFKA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-564: -- Fix Version/s: (was: 0.10.1.0) > Wildcard-based topic consumption should assign partitions to threads uniformly > -- > > Key: KAFKA-564 > URL: https://issues.apache.org/jira/browse/KAFKA-564 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.8.1 >Reporter: Joel Koshy > > Right now, if when a client uses createMessageStreamsByFilter and specifies > 'n' streams (threads), 'n' should be <= the max partition count of any topic. > If it is greater than that, the excess threads will be idle. However, it > would be better to allow a greater number of threads and spread all the > available partitions across the threads. > This should not be too difficult, but may require significant refactoring. > Although it is relevant to current trunk/0.7, we will target this for > post-0.8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-564) Wildcard-based topic consumption should assign partitions to threads uniformly
[ https://issues.apache.org/jira/browse/KAFKA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-564: Fix Version/s: (was: 0.8.1) 0.9.0 > Wildcard-based topic consumption should assign partitions to threads uniformly > -- > > Key: KAFKA-564 > URL: https://issues.apache.org/jira/browse/KAFKA-564 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.8.1 >Reporter: Joel Koshy > Fix For: 0.9.0 > > > Right now, if when a client uses createMessageStreamsByFilter and specifies > 'n' streams (threads), 'n' should be <= the max partition count of any topic. > If it is greater than that, the excess threads will be idle. However, it > would be better to allow a greater number of threads and spread all the > available partitions across the threads. > This should not be too difficult, but may require significant refactoring. > Although it is relevant to current trunk/0.7, we will target this for > post-0.8. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
