You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "xuzq (JIRA)" <ji...@apache.org> on 2017/05/26 06:58:04 UTC
[jira] [Updated] (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:all-tabpanel ]
xuzq updated KAFKA-5331:
------------------------
Attachment: KAFKA-5331.patch
> 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)