What is the current strategy for doing distributed search for Solr?  We
currently have our index divided over 3 servers:
solr1
solr2
solr3

In order to balance the load, our application calls each with a 'shards'
parameter to get the data:
solr1:8080/select?shards=solr1,solr2,solr3...
solr2:8080/select?shards=solr1,solr2,solr3...
solr3:8080/select?shards=solr1,solr2,solr3...

However, with this configuration we seem to be running into problems
(currently running latest build of solr 1.3) with the servers locking up. It
looks like there is some sort of race condition that is causing threads to
lock when hitting the search pretty hard.  In this configuration, each solr
server is responsible for receiving requests, using the shards to send out
additional requests (while also potentially receiving shards requests from
the other two servers), and merging the results before sending back the
response.

Is this the intended design for distributed search for solr?
-- 
View this message in context: 
http://www.nabble.com/Distributed-Search-Strategy---Shards-tp18882112p18882112.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to