kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Narayan Periwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6681) Two instances of kafka consumer reading the same partition within a consumer group
Date Tue, 03 Apr 2018 06:17:00 GMT

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

Narayan Periwal commented on KAFKA-6681:
----------------------------------------

[~yuzhihong@gmail.com], I understand your concern. 0.10.2.1 is a bit old.
The thing is we have not been able to reproduce this in our dev environment even with 0.10.2.1.
We have hit this issue only in production 3 times.
If we are able to find a way to reproduce this in 0.10.2.1, then definitely we can give a
try on 1.1.0. What do you suggest?

> 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)

Mime
View raw message