[
https://issues.apache.org/jira/browse/KAFKA-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589396#comment-16589396
]
John Wilkinson commented on KAFKA-7314:
---------------------------------------
[~omkreddy] As described above, the value of {{bootstrap.servers}} irrelevant
as long as they are valid when resolving DNS. If you have gone through the
example in the docs using two different servers and it works for you, please
post your config and the fact that you could not reproduce.
> MirrorMaker example in documentation does not work
> --------------------------------------------------
>
> Key: KAFKA-7314
> URL: https://issues.apache.org/jira/browse/KAFKA-7314
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
> Reporter: John Wilkinson
> Priority: Critical
>
> Kafka MirrorMaker as described in the documentation
> [here|https://kafka.apache.org/documentation/#basic_ops_mirror_maker] does
> not work. Instead of pulling messages from the consumer-defined
> {{bootstrap.servers}} and pushing to the producer-defined
> {{bootstrap.servers}}, it consumes and producers on the same topic on the
> same host repeatedly.
> To replicate, set up two instances of kafka following
> [this|https://docs.confluent.io/current/installation/docker/docs/installation/recipes/single-node-client.html]
> guide. The schema registry and rest proxy are unnecessary.
> [Here|https://hub.docker.com/r/confluentinc/cp-kafka/] is the DockerHub page
> for the image. The Kafka version is 2.0.0.
> Using those two kafka instances, go {{docker exec}} into one and set up the
> {{consumer.properties}} and the {{producer.properties}} following the
> MirrorMaker guide.
> Oddly, if you put in garbage unresolvable server addresses in the config,
> there will be an error, despite the configs not getting used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
