You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2013/03/28 23:37:15 UTC
[jira] [Commented] (KAFKA-832) 0.8 Consumer prevents rebalance if
consumer thread is blocked or slow
[ https://issues.apache.org/jira/browse/KAFKA-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616742#comment-13616742 ]
Neha Narkhede commented on KAFKA-832:
-------------------------------------
+1, very well thought out. I think shutting down the leader finder thread which will then interrupt the partitionMapLock (if it is blocked on that) will work.
> 0.8 Consumer prevents rebalance if consumer thread is blocked or slow
> ---------------------------------------------------------------------
>
> Key: KAFKA-832
> URL: https://issues.apache.org/jira/browse/KAFKA-832
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Jun Rao
> Priority: Blocker
> Labels: kafka-0.8, p2
> Attachments: kafka-832.patch
>
>
> 0.8 consumer involves multiple locks across the fetcher manager, leader finder thread and the rebalance watcher executor that prevent rebalance from interrupting the consumer. Rebalance should always take precedence over consumption, not the other way around. The effect of this bug is that if a consumer is lagging and the fetcher thread is blocked on adding the next fetched data chunk to the internal blocking queue, rebalance is halted.
--
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