What do you see in the logs? It could be it goes wrong because you have the bootstrap.servers property which is not supported for the old consumer.
On Wed, Mar 9, 2016 at 11:05 AM Gerard Klijs <gerard.kl...@dizzit.com> wrote: > Don't know the actual question, it matters what you want to do. > Just watch out trying to copy every topic using a new consumer, cause then > internal topics are copied, leading to errors. > Here is a temple start script we used: > > #!/usr/bin/env bash > export KAFKA_JMX_OPTS="-Dcom.sun.management.jmxremote=true > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dcom.sun.management.jmxremote.local.only=false > -Djava.rmi.server.hostname=<NODE_HOSTNAME> > -Dcom.sun.management.jmxremote.rmi.port=<MM_JMX_PORT>" > export JMX_PORT=<MM_JMX_PORT> > /usr/bin/kafka-mirror-maker --consumer.config $HOME_DIR/consumer.properties > --producer.config $HOME_DIR/producer.properties --whitelist='<REGEX_MM>' 1>> > $LOG_DIR/mirror-maker.log 2>> $LOG_DIR/mirror-maker.log > > Both the consumer and producer configs have sensible defaults, these are out > consumer.properties template: > > #Consumer template to be used with the mirror maker > zookeeper.connect=<CONSUMER_ZOOKEEPERS> > group.id=mirrormaker > auto.offset.reset=smallest > #next property is not available in new consumer > exclude.internal.topics=true > > *And a producer.properties template:* > > #Producer template to be used with the mirror maker > bootstrap.servers=<PRODUCER_BROKERS> > client.id=mirrormaker > > Because the internal topics can't be excluded in the new consumer yet, we use > the old consumer. > > Hope this helps. > > > On Wed, Mar 9, 2016 at 10:57 AM prabhu v <prabhuvrajp...@gmail.com> wrote: > >> Hi Experts, >> >> I am trying to mirror >> >> >> >> >> -- >> Regards, >> >> Prabhu.V >> >
