You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Nitish Goyal (Jira)" <ji...@apache.org> on 2020/01/20 06:15:00 UTC

[jira] [Comment Edited] (KAFKA-9351) Higher count in destination cluster using Kafka MM2

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

Nitish Goyal edited comment on KAFKA-9351 at 1/20/20 6:14 AM:
--------------------------------------------------------------

[~ryannedolan] Thanks for clarification and update

 

Can you mark this issue as closed/resolved since the above explanation makes sense


was (Author: nitishgoyal13):
[~ryannedolan] Thanks for clarification and update

 

I am making this issue as resolved since the above explanation makes sense

> Higher count in destination cluster using Kafka MM2
> ---------------------------------------------------
>
>                 Key: KAFKA-9351
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9351
>             Project: Kafka
>          Issue Type: Bug
>          Components: mirrormaker
>    Affects Versions: 2.4.0
>            Reporter: Nitish Goyal
>            Priority: Minor
>
> I have setup replication between cluster across different data centres. After setting up replication, at times, I am observing higher event count in destination cluster
> Below are counts in source and destination cluster
>  
> *Source Cluster*
> ```
>  
> events_4:0:51048
> events_4:1:52250
> events_4:2:51526
> ```
>  
> *Destination Cluster*
> ```
> nm5.events_4:0:53289
> nm5.events_4:1:54569
> nm5.events_4:2:53733
> ```
>  
> This is a blocker for us to start using MM2 replicatior



--
This message was sent by Atlassian Jira
(v8.3.4#803005)