[
https://issues.apache.org/jira/browse/KAFKA-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braedon Vickers reopened KAFKA-4600:
------------------------------------
Hi [~guozhang],
I'm going to reopen this, as the issue I raised hasn't been addressed.
[~dana.powers] is correct - this issue is around exceptions thrown by the
`ConsumerRebalanceListener` implementation itself, _not_ about failures in
`SyncGroup`.
https://issues.apache.org/jira/browse/KAFKA-5154 is unrelated, and the [PR you
referenced|https://github.com/apache/kafka/pull/3181] does not fix this issue.
As you can see from the code snipped posted above, the client still catches and
squashes any exception (other than `WakeupException` and `InterruptException`)
raised by `ConsumerRebalanceListener.onPartitionsAssigned()`, causing the issue
described in this ticket.
Regards,
Braedon
> Consumer proceeds on when ConsumerRebalanceListener fails
> ---------------------------------------------------------
>
> Key: KAFKA-4600
> URL: https://issues.apache.org/jira/browse/KAFKA-4600
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.10.1.1
> Reporter: Braedon Vickers
> Priority: Major
> Fix For: 0.11.0.0
>
>
> One of the use cases for a ConsumerRebalanceListener is to load state
> necessary for processing a partition when it is assigned. However, when
> ConsumerRebalanceListener.onPartitionsAssigned() fails for some reason (i.e.
> the state isn't loaded), the error is logged and the consumer proceeds on as
> if nothing happened, happily consuming messages from the new partition. When
> the state is relied upon for correct processing, this can be very bad, e.g.
> data loss can occur.
> It would be better if the error was propagated up so it could be dealt with
> normally. At the very least the assignment should fail so the consumer
> doesn't see any messages from the new partitions, and the rebalance can be
> reattempted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
