kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (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 21:00:00 GMT

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

Ted Yu commented on KAFKA-6681:
-------------------------------

{code}
[2018-03-14 05:04:13,231] ERROR [ReplicaFetcherThread-0-15], Error for partition [adhoc_network_click_ams1_ams1,5]
to broker 15:org.apache.kafka.common.errors.                            NotLeaderForPartitionException:
This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
[2018-03-14 05:04:13,233] ERROR [ReplicaFetcherThread-7-17], Error for partition [cas_rr,21]
to broker 17:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is
   not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
{code}
Did the partition being read by two consumers appear in the ERROR log ?

Thanks

> 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: 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. 
> 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
(v7.6.3#76005)

Mime
View raw message