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, 20 Mar 2018 16:53:00 GMT

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

Narayan Periwal commented on KAFKA-6681:

[~tedyu], Attached the server side logs. Could not retrieve the consumer side logs as it has
hit the retention, I am again trying to reproduce this in our QA setup. See if the server
side logs is of any help.

The server side logs correspond to those node in which the under replicated metrics spiked
during this time

There is no logs in the controller.log file during this time.

> 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: consumer
>    Affects Versions:
>            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 and consumer client version is also 
> 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. 
> During this time, we also see the underreplicated partition metrics spiking. 
> We have hit this twice in production. Please look at it the earliest. 

This message was sent by Atlassian JIRA

View raw message