You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/26 09:35:04 UTC

[jira] [Commented] (KAFKA-5331) MirrorMaker can't guarantee data is consistent between clusters

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

ASF GitHub Bot commented on KAFKA-5331:
---------------------------------------

GitHub user ZanderXu opened a pull request:

    https://github.com/apache/kafka/pull/3151

    KAFKA-5331:MirrorMaker can't guarantee data is consistent between clusters

    this modify is to fix [KAFKA-5331](https://issues.apache.org/jira/browse/KAFKA-5331)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ZanderXu/kafka branch2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3151.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3151
    
----
commit dac18462cd5a0555e397a811f5015cf8f1b145bc
Author: xuzq <xuzq>
Date:   2017-05-26T09:33:01Z

    modify code to fix KAFKA-5331

----


> MirrorMaker can't guarantee data is consistent between clusters
> ---------------------------------------------------------------
>
>                 Key: KAFKA-5331
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5331
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core, tools
>    Affects Versions: 0.10.2.1
>            Reporter: xuzq
>            Priority: Critical
>         Attachments: KAFKA-5331.patch
>
>
> MirrorMaker can't guarantee data is consistent between clusters although the topic partition Numbers are equal.
> If we want to copy data from the old cluster to the new cluster, at the same time guaranteeing the data consistency, we have no choice but to code a MirrorMakerMessageHandler type of class manually to achieve it.
> I think we can add a parameter to say whether or not you want to ensure the order, such as data.consistency and default value is true.
> Of course, you can set data.consistency = false, if you don't want the data in order between clusters or some topic partition Numbers are not equal between clusters.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)