From jira-return-11418-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Mon Apr 2 13:23:03 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id F30E8180627 for ; Mon, 2 Apr 2018 13:23:02 +0200 (CEST) Received: (qmail 89280 invoked by uid 500); 2 Apr 2018 11:23:02 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 89269 invoked by uid 99); 2 Apr 2018 11:23:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2018 11:23:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 87C8EC126F for ; Mon, 2 Apr 2018 11:23:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4KDzZNby3uHY for ; Mon, 2 Apr 2018 11:23:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C3D7E5F19A for ; Mon, 2 Apr 2018 11:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 54578E00A6 for ; Mon, 2 Apr 2018 11:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 13E1A25607 for ; Mon, 2 Apr 2018 11:23:00 +0000 (UTC) Date: Mon, 2 Apr 2018 11:23:00 +0000 (UTC) From: "Narayan Periwal (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-6681) Two instances of kafka consumer reading the same partition within a consumer group MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-6681?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1642= 2150#comment-16422150 ]=20 Narayan Periwal commented on KAFKA-6681: ---------------------------------------- [~yuzhihong@gmail.com] I assume you are asking about this config partition.assignment.strategy. Fo= r this, we are using the default class class org.apache.kafka.clients.consu= mer.RangeAssignor=20 Will this have the issue? > Two instances of kafka consumer reading the same partition within a consu= mer 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=C2=A0 > The issue that we have faced is that, after rebalancing, some of the part= itions gets consumed by 2 instances within a consumer group, leading to dup= lication of the entire partition data.=C2=A0Both the instances=C2=A0continu= e to read until the next rebalancing, or the restart of those clients.=C2= =A0 > 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 in= stance.=C2=A0 > We have hit this twice in production. Please look at it the earliest.=C2= =A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)