[
https://issues.apache.org/jira/browse/KAFKA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995890#comment-14995890
]
Geoff Anderson edited comment on KAFKA-2747 at 11/9/15 12:35 AM:
-----------------------------------------------------------------
Attachment contains reports and logs from a failed mirrormaker hard bounce test
worker1 - source zookeeper
worker3 - source kafka cluster
worker2 - target zookeeper
worker4 - target kafka cluster
was (Author: granders):
Reports and logs from a failed mirrormaker hard bounce test
worker1 - source zookeeper
worker3 - source kafka cluster
worker2 - target zookeeper
worker4 - target kafka cluster
> Message loss if mirror maker is killed with hard kill and then restarted
> ------------------------------------------------------------------------
>
> Key: KAFKA-2747
> URL: https://issues.apache.org/jira/browse/KAFKA-2747
> Project: Kafka
> Issue Type: Bug
> Reporter: Geoff Anderson
> Attachments: 2015-11-08--004-dataloss-newconsumer.tar.gz
>
>
> I recently added simple failover to the existing mirror maker test
> (https://github.com/apache/kafka/pull/427) and found that killing mirror
> maker process with a hard kill resulted in message loss.
> The test here has two single-node broker clusters, one producer producing to
> the source cluster, one consumer consuming from the target cluster, and a
> single mirror maker instance mirroring data between the two clusters.
> mirror maker is using old consumer, zookeeper for offset storage
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
