[
https://issues.apache.org/jira/browse/KAFKA-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431460#comment-15431460
]
Jun Rao commented on KAFKA-4073:
--------------------------------
One way to fix that is to check if the timestamp is present in the source
message in MirrorMaker and if not, use the constructor w/o timestamp (it will
be using the current timestamp).
> MirrorMaker should handle mirroring messages w/o timestamp better
> -----------------------------------------------------------------
>
> Key: KAFKA-4073
> URL: https://issues.apache.org/jira/browse/KAFKA-4073
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.1
> Reporter: Jun Rao
>
> Currently, if the 0.10.0.1 MirrorMaker reads a message w/o timestamp from the
> source cluster, it will hit the following exception. This was introduced in
> KAFKA-3787. So it only affects 0.10.0.1.
> [16/08/2016:18:26:41 PDT] [FATAL] [kafka.tools.MirrorMaker$MirrorMakerThread
> mirrormaker-thread-1]: [mirrormaker-thread-1] Mirror maker thread failure due
> to
> java.lang.IllegalArgumentException: Invalid timestamp -1
> at
> org.apache.kafka.clients.producer.ProducerRecord.<init>(ProducerRecord.java:60)
> at
> kafka.tools.MirrorMaker$defaultMirrorMakerMessageHandler$.handle(MirrorMaker.scala:678)
> at kafka.tools.MirrorMaker$MirrorMakerThread.run(MirrorMaker.scala:414)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
