[
https://issues.apache.org/jira/browse/KAFKA-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-2683.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.9.0.0
Issue resolved by pull request 366
[https://github.com/apache/kafka/pull/366]
> Ensure wakeup exceptions are propagated to user in new consumer
> ---------------------------------------------------------------
>
> Key: KAFKA-2683
> URL: https://issues.apache.org/jira/browse/KAFKA-2683
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Fix For: 0.9.0.0
>
>
> KafkaConsumer.wakeup() can be used to interrupt blocking operations (e.g. in
> order to shutdown), so wakeup exceptions must get propagated to the user.
> Currently, there are several locations in the code where a wakeup exception
> could be caught and silently discarded. For example, when the rebalance
> callback is invoked, we just catch and log all exceptions. In this case, we
> also need to be careful that wakeup exceptions do not affect rebalance
> callback semantics. In particular, it is possible currently for a wakeup to
> cause onPartitionsRevoked to be invoked multiple times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
