[
https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198377#comment-16198377
]
Ronald van de Kuil commented on KAFKA-6022:
-------------------------------------------
Hi Manikumar,
I believe that I have found a little improvement option then
I am at the latest version and the help states that new consumer is the
default.
pi@pi5:/opt/kafka_2.11-0.11.0.0 $ bin/kafka-mirror-maker.sh --help
Option Description
------ -----------
..
--new.consumer Use new consumer in mirror maker (this
is the default).
The current documentation on the kafka site did not mention the --new.consumer
flag. Quite understandable if the --new.consumer is the default.
>From what I have seen in the Kafka Tool the --new.consumer is then not the
>default somewhere deep down in the kafka.tools.MirrorMaker class. That can
>then be improved.
A second option would be to update the documentation.
Switching from zookeeper to kafka to keep track of the kafkaMirror offset ...
how would such an upgrade take place? I bet that it would be advisable to
rebuild the mirror cluster from scratch to prevent duplicates, am I right?
> mirror maker stores offset in zookeeper
> ---------------------------------------
>
> Key: KAFKA-6022
> URL: https://issues.apache.org/jira/browse/KAFKA-6022
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ronald van de Kuil
> Priority: Minor
>
> I happened to notice that the mirror maker stores its offset in zookeeper.
> I do not see it using:
> bin/kafka-consumer-groups.sh --bootstrap-server pi1:9092 --new-consumer --list
> I do however see consumers that store their offset in kafka.
> I would guess that storing the offset in zookeeper is old style?
> Would it be an idea to update the mirror maker to the new consumer style?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
