Hi
I have been working with ElasticSearch for a while now, and find it very
cool. Unfortunately we are no longer allowed to use ElasticSearch in our
project. Therefore we are looking for alternatives - Solr(Cloud) is an
option.
I have been looking at SolrCloud and worked through the "examples" on
http://wiki.apache.org/solr/SolrCloud. I realized that in "Example B:
Simple two shard cluster with shard replicas" you really need an "open"
:-) definition of replica to claim that the shard running at 8900 is a
replica of the one running at 8983. If you index documents into one of
them it is never replicated to the other one. So I guess the only
"connection" between the shards running on 8983 and 8900 is that they
agree that they are running the same logical shard "shard1", and that
any of them can be queried when you want results from shard "shard1".
But results will be different depending on which instance of the shard
you get when you are quering, as soon as you start indexing documents to
one of them AFTER the "cp -r example exampleB".
I order to get the actual replication I guess I need to turn my eyes at
http://wiki.apache.org/solr/SolrReplication, but reading that page I get
a lot in doubt what to do and what not to do now that I am using
SolrCloud. It is all based on replicating config-files around, but my
impression is that SolrCloud takes another approach to configs, namely
that they are kept in ZK. Could you please elaborate on how to use
"real" replication as described on
http://wiki.apache.org/solr/SolrReplication in coexistence with
SolrCloud as described on http://wiki.apache.org/solr/SolrCloud. It
would be nice if the Wiki pages where updated with some kind of
explanation but a reply to this mailing-list posting will also do.
Thanks!
Regards, Per Steffensen
