On 4/8/2016 12:39 AM, Midas A wrote: > we are moving from master slave architecture to solr cloud architecture . > so i would like to know following > > - what kind of challenges we can face on production .
This is extremely difficult to answer. It would depend on the skill level of the admin who does the deployment, and how well they understand SolrCloud. You have this mailing list and the IRC channel as resources to help you through any problems. Frank's response mentions zookeeper as a weak link ... I'm not sure this is true. If there are problems with your networking or your server stability, then zookeeper may have issues, but these are not problems with zookeeper itself. > - Is there any drawback of solrcloud Depends on whether you consider "three servers minimum" (for zookeeper) for a fault-tolerant install to be a drawback or not. SolrCloud is a slightly more difficult to set up, but tends to be easier to maintain after install. > - How solr cloud distributes requests between nodes and how node will > behave on heavy traffic . For indexing, cloud forwards new documents to the leader of the correct shard. The leader of the shard will index the documents locally and also send those documents to all other replicas for that shard, which will each index them independently. For queries, cloud will randomly pick replicas in the cloud to serve requests. If there are replicas for the requested collection on the local machine, the request *might* be served locally rather than traverse the network again. > - Is there any way to shard node with custom logic You could probably write your own custom Router class and change the router on the collection to use it, although I do not know how to do this. Once somebody finds out, a page on the old wiki, with a code example, would be a good idea. I don't know if that kind of documentation belongs in the reference guide. Thanks, Shawn
