Hey Shawn, others. This is a pitfall that Solr users seem to run into with some frequency. (Anecdotally, I've bookmarked the Lucidworks article you referenced because I end up referring people to it often enough.)
The immediate first advice when someone encounters these onDeckSearcher error messages is to examine their commit settings. Is there any other possible cause for those messages? If not, can we consider changing the log/exception error message to be more explicit about the cause? A strawman new message could be: "Performance warning: Overlapping onDeskSearchers=2; consider reducing commit frequency if performance problems encountered" Happy to create a JIRA/patch for this; just wanted to get some feedback first in case there's an obvious reason the messages don't get explicit about the cause. Jason On Wed, May 17, 2017 at 8:49 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 5/17/2017 5:57 AM, Srinivas Kashyap wrote: >> We are using Solr 5.2.1 version and are currently experiencing below Warning >> in Solr Logging Console: >> >> Performance warning: Overlapping onDeskSearchers=2 >> >> Also we encounter, >> >> org.apache.solr.common.SolrException: Error opening new searcher. exceeded >> limit of maxWarmingSearchers=2, try again later. >> >> >> The reason being, we are doing mass update on our application and solr >> experiencing the higher loads at times. Data is being indexed using DIH(sql >> queries). >> >> In solrconfig.xml below is the code. >> >> <!-- >> <autoCommit> >> <maxDocs>10000</maxDocs> >> <maxTime>1000</maxTime> >> </autoCommit> >> --> >> >> Should we be uncommenting the above lines and try to avoid this error? >> Please help me. > > This warning means that you are committing so frequently that there are > already two searchers warming when you start another commit. > > DIH does a commit exactly once -- at the end of the import. One import will > not cause the warning message you're seeing, so if there is one import > happening at a time, either you are sending explicit commit requests during > the import, or you have autoSoftCommit enabled with values that are far too > small. > > You should definitely have autoCommit configured, but I would remove > maxDocs and set maxTime to something like 60000 -- one minute. The > autoCommit should also set openSearcher to false. This kind of commit > will not make new changes visible, but it will start a new transaction > log frequently. > > <autoCommit> > <maxTime>60000</maxTime> > <openSearcher>false</openSearcher> > </autoCommit> > > An automatic commit (soft or hard) with a one second interval is going to > cause that warning you're seeing. > > https://lucidworks.com/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ > > Thanks, > Shawn >
