Yes, that is probably the cause. I think you have very aggressive commit rates and Solr is not able to keep up. If you are sending explicit commits, switch to using autoCommit with openSearcher=false every 5-10 minutes (this depends on your indexing rate) and autoSoftCommit every 2-5 minutes. Adjust as necessary.
On Sat, Dec 12, 2015 at 10:08 PM, Adrian Liew <adrian.l...@avanade.com> wrote: > Hi there, > > I am using Solr Cloud 5.3.0 on a multiserver cluster (3 servers to mention) > whereby each server spec is at 16 core and 32 GB Ram. > > I am facing regular errors - Error sending update to http://someip:8983/solr > - "Timeout occured while waiting response from server at server a" ... > Caused by java.net.SocketTimeoutException: Read Timed out. > > I am not sure if this error can be caused due to some preceding warnings > reported such as > > Error sending update to http://someip:8983/solr - > org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error > from server at http://someip:8983/solr/sitecore_master_index_shard1_replica3: > Error opening new searcher. exceeded limit of maxWarmingSearchers=6 > > Can the maxWarmingSearchers error possibly cause the read timeouts to occur? > If yes, when maxWarmingSearchers warning is addressed, will that remove the > errors for the read timeouts? > > Best regards, > Adrian > -- Regards, Shalin Shekhar Mangar.
