[
https://issues.apache.org/jira/browse/KAFKA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991026#comment-14991026
]
Jiangjie Qin commented on KAFKA-2747:
-------------------------------------
[~geoffra], could you verify the following two things?
1. Is the group id of consumer the same after mirror maker restarts?
2. Is the committed offset out of range after mirror maker restarts?
Both are caused by the fact that we are setting the auto.offset.reset to
largest.
> 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
>
> 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)
