[ 
https://issues.apache.org/jira/browse/KAFKA-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523095#comment-16523095
 ] 

Narayan Periwal edited comment on KAFKA-6681 at 6/26/18 4:02 AM:
-----------------------------------------------------------------

[~steven.aerts], We are using RangeAssignor(which is the default), and not the 
Sticky Assignor which KAFKA-7026 mentions of.

Some observation is that there is spike in the number of UnderReplicated 
partition, after which multiple consumer instances start consuming the same 
topic partition

Our Kafka brokers and consumer both are in version 0.10.2.1


was (Author: nperiwal):
[~steven.aerts], We are using RangeAssignor(which is the default), and not the 
Sticky Assignor which KAFKA-7026 mentions of.

> Two instances of kafka consumer reading the same partition within a consumer 
> group
> ----------------------------------------------------------------------------------
>
>                 Key: KAFKA-6681
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6681
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>    Affects Versions: 0.10.2.1
>            Reporter: Narayan Periwal
>            Priority: Critical
>         Attachments: server-1.log, server-2.log
>
>
> We have seen this issue with the Kafka consumer, the new library that got 
> introduced in 0.9
> With this new client, the group management is done by kafka coordinator, 
> which is one of the kafka broker.
> We are using Kafka broker 0.10.2.1 and consumer client version is also 
> 0.10.2.1 
> The issue that we have faced is that, after rebalancing, some of the 
> partitions gets consumed by 2 instances within a consumer group, leading to 
> duplication of the entire partition data. Both the instances continue to read 
> until the next rebalancing, or the restart of those clients. 
> It looks like that a particular consumer goes on fetching the data from a 
> partition, but the broker is not able to identify this "stale" consumer 
> instance. 
> We have hit this twice in production. Please look at it the earliest. 



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

Reply via email to