You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2015/12/01 06:34:11 UTC

[jira] [Resolved] (KAFKA-2913) GroupMetadataManager unloads all groups in removeGroupsForPartitions

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

Guozhang Wang resolved KAFKA-2913.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.0.1

Issue resolved by pull request 605
[https://github.com/apache/kafka/pull/605]

> GroupMetadataManager unloads all groups in removeGroupsForPartitions
> --------------------------------------------------------------------
>
>                 Key: KAFKA-2913
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2913
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 0.9.0.1
>
>
> In GroupMetadataManager.removeGroupsForPartition, we currently remove all groups from the cache, but we should only be removing groups for the respective partition. This will cause an unneeded rebalance for groups mistakenly removed. And since the generation would reset to 0 in this case, the offsets from the current generation would be rejected and the consumer would see duplicates.



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