What exactly is your motivation? I mean, the primary benefit of SolrCloud is better support for sharding, and you have only a single shard. If you have no need for sharding and your master-slave replicated Solr has been working fine, then stick with it. If only one machine is having a load problem, then that one node should be replaced. There are indeed plenty of good reasons to prefer SolrCloud over traditional master-slave replication, but so far you haven't touched on any of them.
How much data (number of documents) do you have? What is your typical query latency? -- Jack Krupansky On Wed, Feb 10, 2016 at 2:15 AM, kshitij tyagi <kshitij.shopcl...@gmail.com> wrote: > Hi, > > We are currently using solr 5.2 and I need to move on solr cloud > architecture. > > As of now we are using 5 machines : > > 1. I am using 1 master where we are indexing ourdata. > 2. I replicate my data on other machines > > One or the other machine keeps on showing high load so I am planning to > move on solr cloud. > > Need help on following : > > 1. What should be my architecture in case of 5 machines to keep (zookeeper, > shards, core). > > 2. How to add a node. > > 3. what are the exact steps/process I need to follow in order to change to > solr cloud. > > 4. How indexing will work in solr cloud as of now I am using mysql query to > get the data on master and then index the same (how I need to change this > in case of solr cloud). > > Regards, > Kshitij >
