The same test w/ XML format has no such problem. But with binary update format it is throwing error
On Tue, Jan 6, 2009 at 10:42 AM, Noble Paul നോബിള് नोब्ळ् <[email protected]> wrote: > This is a JUnit test (which patch in the JIRA). > > I am not doing anything other than the LargeVolumeJettyTest . > --Noble > > > On Tue, Jan 6, 2009 at 10:37 AM, Otis Gospodnetic > <[email protected]> wrote: >> Doesn't that mean that you are doing something that causes searchers to warm >> up (e.g. running snap* scripts or your new replication equivalent) and doing >> that so frequently that when you do this for the third time the first two >> searchers are still warming up? >> >> >> Otis >> -- >> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch >> >> >> >> ----- Original Message ---- >>> From: Noble Paul നോബിള് नोब्ळ् <[email protected]> >>> To: [email protected] >>> Sent: Monday, January 5, 2009 11:10:06 PM >>> Subject: error: exceeded limit of maxWarmingSearcher >>> >>> I have implemented the javabin update functionality (SOLR-8965) and >>> the LargeVolumeJettytestcase is failing with the following message. >>> >>> >>> exceeded limit of maxWarmingSearchers=2, try again later. >>> Jan 5, 2009 5:44:40 PM >>> org.apache.solr.update.processor.LogUpdateProcessor finish >>> INFO: {} 0 15 >>> Jan 5, 2009 5:44:40 PM org.apache.solr.common.SolrException log >>> SEVERE: org.apache.solr.common.SolrException: Error opening new >>> searcher. exceeded limit of maxWarmingSearchers=2, try again later. >>> at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1050) >>> at >>> org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:350) >>> at >>> org.apache.solr.update.processor.RunUpdateProcessor.processCommit(RunUpdateProcessorFactory.java:78) >>> at >>> org.apache.solr.handler.BinaryUpdateRequestHandler.parseAndLoadDocs(BinaryUpdateRequestHandler.java:95) >>> >>> Can anyone point me to what I may be doing wrong? >>> -- >>> --Noble Paul >> >> > > > > -- > --Noble Paul > -- --Noble Paul
