Often the limiting factor is, indeed, the Tomcat settings. Remember that each Solr server has to talk to other Solr servers hosting shards, so if you have 10 shards a single request requires 10 connections from the aggregating node to the other shards so the total number of connections can to up fast.
And bump it up quite high, 10,000 comes to mind but that might be threads I'm thinking of... Before you go there, though, if your Solr instances are pegging their respective CPUs, then upping the max threads and/or connections won't do much good, it's something to check first. Best, Erick On Wed, Nov 25, 2015 at 3:29 PM, Vincenzo D'Amore <v.dam...@gmail.com> wrote: > Hi all, > > I have a SolrCloud cluster that is not scaling properly. > As far as I can see, reached a certain number of connection (maybe 30/40) > the cluster stops to until the running queries are completed. > And only then it starts to work on queue. > So the queue grows up and the waiting time become longer. > All the pending requests are handled but, after 10 seconds, all the > connections timed out. > > Now I'm thinking to raise the number of concurrent worked connections. > Now having a look at solr cloud configuration, I see there should be a > shardHandler in solrconfig.xml. > > But I was unable to find any parameter like <shardHandler> or even > maxConnectionsPerHost inside my configuration. > > Where is current configuration? I have tried even with Jconsole, but > without success. > > SolrCloud 4.8.1 is running in tomcat, should I configure tomcat instead of > Solrcloud? > > Best regards, > Vincenzo D'Amore > > > -- > Vincenzo D'Amore > email: v.dam...@gmail.com > skype: free.dev > mobile: +39 349 8513251
