lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky" <>
Subject Re: Understanding query behaviour in LBHttpSolrServer
Date Fri, 18 Jul 2014 12:58:06 GMT
For traditional, non-SolrCloud "distributed" mode, load balancing and 
sharded queries are independent concepts - you can use them each separately 
or together at your choice. If you want the query to be sharded for a 
non-SolrCloud Solr server, then you need to pass the "shards" parameter on 
each query. For SolrCloud the sharding of queries takes place automatically 
without any shards parameter. But you should use the CloudSolrServer for 
load balancing of SolrCloud anyway - internally it does the load balancing 
automatically based on discovery of the SolrCloud configuration.

-- Jack Krupansky

-----Original Message----- 
From: search engn dev
Sent: Friday, July 18, 2014 1:15 AM
Subject: Understanding query behaviour in LBHttpSolrServer

I just want to understand query flow and how load balancing works in case of
LBHttpSolrServer. We have setup SolrCloud with one collection, and that
collection has 4 shards and each shard has two nodes i.e one master and one

I have configured LBHttpSolrServer as below.
SolrServer lbHttpSolrServer = new

>From my understanding solr and solrj works as below,
1. LBHttpSolrServer keeps pinging above list of servers and maintains list
of live servers.
2. Every time query arives it picks one server from the list (round-robin
3. Sends query to selected server server.
4. When query arives at solr node it internally distributes query to
remaining shards , collects,merges,ranks results and sends response back to
the user.

Here my confusion is at point number 4, is my understanding correct? if not
please correct. And do i need to pass all 8 nodes to LBHttpSolrServer or
just 4 will be sufficient .

View this message in context:
Sent from the Solr - User mailing list archive at 

View raw message