[
https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472688#comment-13472688
]
Joel Koshy commented on KAFKA-550:
----------------------------------
Another point to consider for future enhancement is that right now all wildcard
topics will be assigned
num-threads (i.e., the wildcard stream count) threads regardless of how many
partitions
they have.
Ideally, the user should be able to say something like "numThreads=100" and
messages from all
topic-partitions (that are allowed by the wildcard) should be fed into those
queues/streams uniformly.
> Wildcarded consumption is single-threaded
> -----------------------------------------
>
> Key: KAFKA-550
> URL: https://issues.apache.org/jira/browse/KAFKA-550
> Project: Kafka
> Issue Type: Bug
> Reporter: Joel Koshy
> Assignee: Joel Koshy
> Attachments: KAFKA-550-v1.patch, KAFKA-550-v2.patch
>
>
> It's surprising that we haven't noticed this before, but I was looking at a
> CPU usage profile on yourkit and It turns out that only one mirror maker
> thread is actually doing anything. Basically I suspect some bug in fetcher ->
> queue mapping. Only one queue seems to have any data. I'll look into this
> probably next week.
--
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
