On 8/11/2015 6:15 AM, Adrian Liew wrote: > I am not sure if you know much about the Sitecore WCMS Platform and we > are experiencing some issues reported by Solr Admin with regards to > the following when we try to publish some content in order to trigger > an index update to our sitecore_web_index SolrCore: > > > > 1. 8/11/2015, 7:46:26 PM > > WARN > > null > > SolrCore > > [sitecore_master_index] Error opening new searcher. exceeded limit of > maxWarmingSearchers=2, try again later. > > > 2. 8/11/2015, 7:46:26 PM > > ERROR > > null > > SolrCore > > org.apache.solr.common.SolrException: Error opening new searcher. > exceeded limit of maxWarmingSearchers=2, try again later. > > > > I also noticed that I had been receiving a quick succession of commits > over time which I think is causing the above. I read somewhere in one > of your articles after googling abit on the problem, and you did > mention enabling autocommits may work? >
First, a little housekeeping regarding the way this message found its way to me: http://people.apache.org/~hossman/#private_q I'm redirecting this reply to the list (with a bcc to you) because there's nothing sensitive in your question or my reply, and this information may help others. Those log messages are almost always caused by committing too frequently. Specifically, commits with openSearcher=true (which is the default), which makes changes to the index visible to queries. The commits need to be adjusted so they are as infrequent as you can possibly make them. A bunch of good information about commits and their pitfalls can be found here: http://lucidworks.com/blog/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ In particular, pay attention to the part about not listening your product manager who says "we need no more than 1 second latency". This is a common design requirement passed down from managers and executives who have no idea how a search index works. When actual user behavior and expectations are considered, making changes visible within one minute or five minutes is usually enough. Even for unusual situations, ten or fifteen seconds of latency is usually OK. I checked the solr-user list history for your message threads, and tried to find this Sitecore software you mentioned. It appears that even downloading the binary requires registration, which I'm not going to do for software I have no plans to use myself, and I'm more interested in the source code than the binary. I couldn't find any source code. It looks like this is a commercial product that doesn't provide code. Are there any commit-related settings in your configuration for the sitecore product? I found this: http://www.sitecore.net/learn/blogs/technical-blogs/sitecore-7-development-team/posts/2013/04/sitecore-7-commit-policies.aspx Regardless of what happens with this message and its replies, I recommend that you open a trouble ticket with Sitecore, since there is probably a good chance that you've paid them for their software. If they are competent, they will know about how Solr commits work and will have some suggestions for you to try. If it turns out that the Sitecore commit settings are reasonable, then the problem is likely happening because commits are happening very slowly. We may need to look into how you can improve general Solr performance. There is a very small amount of information about slow commits on this page: https://wiki.apache.org/solr/SolrPerformanceProblems#Slow_commits Thanks, Shawn
