My first reaction to your question is why are you running thousands of queries in a loop? Immediately, I think this will not scale well and the design probably needs to be re-visited.
Second, if you need that many requests, then you need to seriously consider an architecture that supports it. This will require a complex design involving load balancers, multiple servers, replication, etc. People have achieved this with Solr, but it's beyond the scope of Solr itself to provide this, as its a matter of system architecture. Also, there are limits to the number of app server threads allowed, OS threads allowed, OS sockets, OS file descriptors, etc. etc. All of which need to be understood, designed for and configured properly. <br><br><br>------- Original Message ------- On 4/10/2012 07:51 AM arunssasidhar wrote:<br>We have a PHP web application which is using SOLR for searching. The APP is <br>using CURL to connect to the SOLR server and which run in a loop with <br>thousands of predefined keywords. That will create thousands of different <br>search quires to SOLR at a given time. <br> <br>My issue is that, when a single user logged into the app everything is <br>working as expected. When there is more than one user is trying to run the <br>app we are getting this response from the server. <br> <br> Failed to connect to xxx.xxx.xxx.xxx: Cannot assign requested <br>addressFailed to connect to xxx.xxx.xxx.xxx: Cannot assign requested <br>addressFailed <br> <br>Our assumption is that, SOLR server is unable to handle this much search <br>queries at a given time. If so what is the solution to overcome this?. Is <br>there any settings like keep-alive in SOLR? <br> <br>Any help would be highly appreciate. <br> <br>Thanks, <br> <br>Arun S <br> <br> <br>-- <br>View this message in context: http://lucene.472066.n3.nabble.com/SOLR-issue-too-many-search-queries-tp3899518p3899518.html <br>Sent from the Solr - User mailing list archive at Nabble.com. <br> <br>
