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/09 01:12:02 UTC

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

     [ https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Koshy updated KAFKA-550:
-----------------------------

    Attachment: KAFKA-550-v1.patch

This was a silly coding bug - the topicThreadIdAndQueues map was getting
updated incorrectly.  This affects both 0.7 and 0.8. The same patch applies to
both trunk and 0.8.

The patch fixes the issue. Also got rid of the implicit def in
reinitializeConsumer.

                
> 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