[
https://issues.apache.org/jira/browse/KAFKA-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033126#comment-15033126
]
ASF GitHub Bot commented on KAFKA-2913:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/605
KAFKA-2913: missing partition check when removing groups from cache
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-2913
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/605.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #605
----
commit 3ae8d9171b4cb0b87e198e4b87907369ade9e0d7
Author: Jason Gustafson <[email protected]>
Date: 2015-12-01T05:23:21Z
KAFKA-2913: missing partition check when removing groups from cache
----
> 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
>
> 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)
