You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Joel Koshy (JIRA)" <ji...@apache.org> on 2012/10/10 18:43:02 UTC
[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 ]
Joel Koshy updated KAFKA-564:
-----------------------------
Description:
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.
was:
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.
> 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.8.1
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira