On 8/18/2015 8:18 AM, Rallavagu wrote: > Thanks for the response. Does this cache behavior influence the delay > in catching up with cloud? How can we explain solr cloud replication > and what are the option to monitor and take proactive action (such as > initializing, pausing etc) if needed?
I don't know enough about your setup to speculate. I did notice this exception in a previous reply: org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for connection from pool I can think of two things that would cause this. One cause is that your servlet container is limiting the number of available threads. A typical jetty or tomcat default for maxThreads is 200, which can easily be exceeded by a small Solr install, especially if it's SolrCloud. The jetty included with Solr sets maxThreads to 10000, which is effectively unlimited except for extremely large installs. If you are providing your own container, this will almost certainly need to be raised. The other cause is that your install is extremely busy and you have run out of available HttpClient connections. The solution in this case is to increase the maximum number of connections per host in the HttpShardHandler config, which defaults to 20. https://wiki.apache.org/solr/SolrConfigXml#Configuration_of_Shard_Handlers_for_Distributed_searches There might be other causes for that exception, but I think those are the most common causes. Depending on how things are set up, you have problems with both. Thanks, Shawn
