kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Narayan Periwal <narayan.peri...@inmobi.com>
Subject Re: Two instances of Kafka consumer reading same partition
Date Thu, 29 Mar 2018 16:57:19 GMT
Hi,

We had one more of such an issue, and looks like such issues are coming
more frequently, whenever there is some issue in the kafka cluster.
This time, I could retrieve both the server and client side logs, have
added the detail in the same ticket - KAFKA-6681
<https://issues.apache.org/jira/browse/KAFKA-6681>

Any help will be highly appreciated.

Thanks,
Narayan

On Mon, Mar 19, 2018 at 6:45 PM, Narayan Periwal <narayan.periwal@inmobi.com
> wrote:

> Hi,
>
> We are facing an issue with the Kafka consumer,  the new library that got
> introduced in 0.9
>
> 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 the same partition until the next rebalancing, or the restart of those
> clients.
>
> Have incorporated the details in this ticket - KAFKA-6681
> <https://issues.apache.org/jira/browse/KAFKA-6681>
>
> Please look at it the earliest
>
> Regards,
> Narayan
>



-- 
Thanks,
Narayan

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message