LBHttpSolrServer is only solrj feature.. doesn't it? I think that Solr does not balance queries among cores in the same server. You can claim that it's a non-issue, if a single core can completely serve multiple queries on the same time, and passing requests through different cores does nothing. I feel that we can achieve some improvement in this case...
On Mon, Feb 4, 2013 at 12:45 AM, Shawn Heisey <s...@elyograg.org> wrote: > On 2/3/2013 3:24 PM, Isaac Hebsh wrote: > >> Thanks Shawn for your quick answer. >> >> When using collection name, Solr will choose the leader, when available in >> the current server (see getCoreByCollection in SolrDispatchFilter). It is >> clear that it's useful when indexing. But queries should run on replicas >> too, don't they? Moreover, the core selection seems to be consistent (that >> is, it will never get the non-first core in a specific arrangement)... >> >> Under the assumption that a core makes extra work for serving queries >> (e.g, >> combining results, processing every non distributed search component (?)), >> and the assumption that multithreading works well here, Is utilizing all >> the cores would not be useful? >> > > Here's an excerpt from the SolrCloud wiki page that suggests it handles > load balancing across the cluster automatically: > > **** > Now send a query to any of the servers to query the cluster: > > http://localhost:7500/solr/**collection1/select?q=*:*<http://localhost:7500/solr/collection1/select?q=*:*> > > Send this query multiple times and observe the logs from the solr servers. > You should be able to observe Solr load balancing the requests (done via > LBHttpSolrServer ?) across replicas, using different servers to satisfy > each request. > **** > > This is near the end of example B. > > http://wiki.apache.org/solr/**SolrCloud#Example_B:_Simple_** > two_shard_cluster_with_shard_**replicas<http://wiki.apache.org/solr/SolrCloud#Example_B:_Simple_two_shard_cluster_with_shard_replicas> > > Thanks, > Shawn > >
