You can override the default number of partitions on the source and target cluster to N. (num.partitions in the broker config). If you need a higher (or lower) number of partitions for specific topics you can override that on a per-topic basis (again, the config can be kept identical between the source and target cluster).
On Tue, Jul 2, 2013 at 1:26 PM, Yu, Libo <[EMAIL PROTECTED]> wrote:
For a topic with N partitions on the source cluster, if I let mirrormaker to create topic automatically, the same topic on the destination cluster will have only one partition. Is that expected behavior? Could you just give a yes/no answer? Thanks.
Thanks, Jun. Previously I created the topic with the specified number of partitions on the destination (target) cluster before I launched mirrormaker to do mirroring. But the mirrormaker only downloaded data for some of partitions, and in some cases, it stopped randomly. I will test this scenario again with beta1.
num.partition will set a number of partition for all topics. If the topics have different partition numbers, then this will not work.
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext