Hi Otis 

It's exactly what happening to me ... what would you reckon .. I've tws
searchers still on .. how can I stop this ...
I just started my commit every 5mn .. 
with auto snapshot afeter commit.

I don't know what can I do,
thanks A LOT


Otis Gospodnetic 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
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/error%3A-exceeded-limit-of-maxWarmingSearcher-tp21304433p21811067.html
Sent from the Solr - Dev mailing list archive at Nabble.com.

Reply via email to