You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2012/10/09 07:52:03 UTC

[jira] [Commented] (KAFKA-550) Wildcarded consumption is single-threaded

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

Jun Rao commented on KAFKA-550:
-------------------------------

Thanks for the patch. What was the bug? Is it the implicit function? 

1.reinitializeConsumer(): It seems that the computation for threadQueueStreamPairs is slightly different for WildcardTopicCount and StaticTopicCount. However, it seems that we can just use the same computation. 
                
> 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
>
>
> 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