Hi, How are you executing searches?
I am asking because if you search using Solr client, for example SolrJ - ie. create instance of CloudSolrClient, and not directly via HTTP endpoint, it will provided load-balancing (last time I checked it picks random non-stale node). Thanks, Jarek On Mon, 18 Apr 2016, at 05:58, John Bickerstaff wrote: > Thanks, so on the matter of indexing -- while I could isolate a cloud > replica from queries by not including it in the load balancer's list... > > ... I cannot isolate any of the replicas from an indexing perspective by > a > similar strategy because the SOLR leader decides who does indexing? Or > do > all "nodes" index the same incoming document independently? > > Now that I know I still need a load balancer, I guess I'm trying to find > a > way to keep indexing load off servers that are busy serving search > results... Possibly by having one or two servers just handle indexing... > > Perhaps I'm looking in the wrong direction though -- and should just spin > up more replicas to handle more indexing load? > On Apr 17, 2016 10:46 PM, "Walter Underwood" <wun...@wunderwood.org> > wrote: > > No, Zookeeper is used for managing the locations of replicas and the > leader > for indexing. Queries should still be distributed with a load balancer. > > Queries do NOT go through Zookeeper. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > > > > On Apr 17, 2016, at 9:35 PM, John Bickerstaff <j...@johnbickerstaff.com> > wrote: > > > > My prior use of SOLR in production was pre SOLR cloud. We put a > > round-robin load balancer in front of replicas for searching. > > > > Do I understand correctly that a load balancer is unnecessary with SOLR > > Cloud? I. E. -- SOLR and Zookeeper will balance the load, regardless of > > which replica's URL is getting hit? > > > > Are there any caveats? > > > > Thanks,
