Hi to all,
I started following this mailing list about 1 month ago and I read many
threads about SolrCloud and distributed Solr. I just want to check if I
understood correctly and, if so, ask for some architectural decision I have
to take:
1) At the moment, in order to design a scalable Solr deployment, one could
choose if to setup a Solr cloud (where servers are transparent to the
client) or a simil-Solr cloud (distributed mode) where client has to know
which server to contact, right?
2) If so, I don't fully understand why to make the clients aware about the
Solr servers. Why should a client decide on its own where to index or
query? Is it because of backward compatibility, performance or similar
issues? From what I understood SolrCloud does all the magic hiding to the
user the real deployment (with all subsequent benefits of tearing up/down
server and so on)...isn't it?
3) When configuring SolrCloud I put in the solrconfig.xml the list of the
shards supporting my collection distribution. E.g.:
<str name="self">localhost:8983/solr</str>
<arr name="shards">
<str>localhost:8983/solr</str>
<str>someotherhost:7574/solr</str>
</arr>
How does the splitting work behind the scenes (a link to a detailed
explanation is sufficient..)?
4) If one day I decide to add one more server to distribute the load, what
is the correct procedure to deploy such a change? Does SolrCloud
automatically redistribute the index within all shards?
Best,
Flavio
