On 9/13/2013 10:16 AM, Branham, Jeremy [HR] wrote:
Currently, our SOLR 1.3 installation shares 4 applications servers with other
Java apps, leveraging master/slave replication.
To get application isolation, we are moving from SOLR 1.3 to 4.3 and acquiring
2 new production [vm] servers for the migration.
For the new SOLR configuration, we are considering leveraging SOLR Cloud, but
there would be no shard redundancy with only 2 servers.
Are there any good reasons to use a 2 shard cloud setup with no redundancy
versus a Master/Slave configuration on SOLR 4.3?
You should go to Solr 4.4, not 4.3. Version 4.5 will be out soon, so
unless you're going to go live before 2-3 weeks go by, you should
probably plan on going with 4.5 instead. Version 4.5 would be a
*really* good idea if you're going to use SolrCloud, as there are
significant indexing improvements coming.
With SolrCloud, you can have shard redundancy with two servers. All
shards will exist on both servers. What you won't have with only two
servers is zookeeper redundancy, and zookeeper is *critical* for
SolrCloud. If you can add a third server with minimal CPU/RAM that's
just for zookeeper, you can have that redundancy with no problem. This
is what I have done for my small cloud install. It's the sort of thing
that you could even just throw a desktop computer on the network to do,
as long as you monitor it really well so you know if it ever goes down.
My large main Solr install is two completely independent sharded index
copies *WITHOUT* SolrCloud. It's been that way since Solr 3.x because
master/slave replication is too inflexible.
Thanks,
Shawn
