You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Onur Karaman (JIRA)" <ji...@apache.org> on 2015/09/18 20:37:04 UTC

[jira] [Updated] (KAFKA-2557) Separate RebalanceInProgress from IllegalGeneration Error Code

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

Onur Karaman updated KAFKA-2557:
--------------------------------
    Summary: Separate RebalanceInProgress from IllegalGeneration Error Code  (was: Separate RebalanceNeededException from IllegalGenerationIdException)

> Separate RebalanceInProgress from IllegalGeneration Error Code
> --------------------------------------------------------------
>
>                 Key: KAFKA-2557
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2557
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>            Reporter: Jiangjie Qin
>            Assignee: Onur Karaman
>
> The IllegalGenerationIdException is a bit confusing today. When a consumer receives an IllegalGenerationIdException from hearbeat response, it should still use that generation id to commit offset. i.e. the generation ID was not really illegal. 
> The current code was written earlier when we still bump up the generation ID when the coordinator enters PrepareRebalance state. Since now the generation ID is bumped up after PreareRebalance state ends, we should not overload IllegalGenerationIdException to notify a rebalance but create a new error code such as RebalanceNeededException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)