Thanks for answering
Mark Miller skrev:
Guess that is the whole point. Guess that I do not have to replicate
configuration files, since SolrCloud (AFAIK) does not use local
configuration files but information in ZK. And the it gets a little hard to
guess how to do it, since the explanation on http://wiki.apache.org/solr/*
*SolrReplication <http://wiki.apache.org/solr/SolrReplication> talkes
about different configs for master and slave. How to acheive that when the
config is shared (in ZK).
You can System properties to allow a config to be used both for a slave and
a master. You could also just not configure as a slave or master and try
doing one off snap pulls with a chron job or something.
Thanks
We have not hooked up SolrCloud with replication because the new SolrCloud
work happening on the solrcloud branch will only use it for recovery.
Rather than replicate, added documents will simply be forwarded to all
replicas so you can also use Near Realtime and to provide better
consistency.
Sounds like the right solution to me!
