You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Richard Yu (JIRA)" <ji...@apache.org> on 2018/07/10 01:55:00 UTC

[jira] [Issue Comment Deleted] (KAFKA-4693) Consumer subscription change during rebalance causes exception

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

Richard Yu updated KAFKA-4693:
------------------------------
    Comment: was deleted

(was: Hi [~hachikuji] Is the validation performed when the request future succeeds (i.e. something that occurs after {{ConsumerRebalanceListener}}'s method is called) ? Because when I first ran through the code, there does not appear to be any place where there looks to be such a validation. (I was looking in the proximity of {{ConsumerCoordinator#onJoinComplete()}}))

> Consumer subscription change during rebalance causes exception
> --------------------------------------------------------------
>
>                 Key: KAFKA-4693
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4693
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>            Reporter: Jason Gustafson
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> After every rebalance, the consumer validates that the assignment received contains only partitions from topics that were subscribed. If not, then we raise an exception to the user. It is possible for a wakeup or an interrupt to leave the consumer with a rebalance in progress (e.g. with a JoinGroup to the coordinator in-flight). If the user then changes the topic subscription, then this validation upon completion of the rebalance will fail. We should probably detect the subscription change, eat the exception, and request another rebalance. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)