You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com> on 2009/01/06 05:10:06 UTC
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
Re: error: exceeded limit of maxWarmingSearcher
Posted by sunnyfr <jo...@gmail.com>.
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 നോബിള് नोब्ळ् <no...@gmail.com>
>> To: solr-dev@lucene.apache.org
>> 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.
Re: error: exceeded limit of maxWarmingSearcher
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
I found it out. The ContentStreamHandlerBase also calls commit
thanks
--Noble
On Tue, Jan 6, 2009 at 8:29 PM, Yonik Seeley <ys...@gmail.com> wrote:
> On Tue, Jan 6, 2009 at 12:14 AM, Noble Paul നോബിള് नोब्ळ्
> <no...@gmail.com> wrote:
>> The same test w/ XML format has no such problem. But with binary
>> update format it is throwing error
>
> Perhaps something is being set on the update command that is causing
> too many commits (commitWithin or something like that?) Try counting
> the number of commits that happen with XML vs binary.
>
> There's an outside possibility that faster/smaller binary format is
> triggering an edge case in the test... that's a real stretch though.
>
> -Yonik
>
>> On Tue, Jan 6, 2009 at 10:42 AM, Noble Paul നോബിള് नोब्ळ्
>> <no...@gmail.com> 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
>>> <ot...@yahoo.com> 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 നോബിള് नोब्ळ् <no...@gmail.com>
>>>>> To: solr-dev@lucene.apache.org
>>>>> 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
>>
>
--
--Noble Paul
Re: error: exceeded limit of maxWarmingSearcher
Posted by Yonik Seeley <ys...@gmail.com>.
On Tue, Jan 6, 2009 at 12:14 AM, Noble Paul നോബിള് नोब्ळ्
<no...@gmail.com> wrote:
> The same test w/ XML format has no such problem. But with binary
> update format it is throwing error
Perhaps something is being set on the update command that is causing
too many commits (commitWithin or something like that?) Try counting
the number of commits that happen with XML vs binary.
There's an outside possibility that faster/smaller binary format is
triggering an edge case in the test... that's a real stretch though.
-Yonik
> On Tue, Jan 6, 2009 at 10:42 AM, Noble Paul നോബിള് नोब्ळ्
> <no...@gmail.com> 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
>> <ot...@yahoo.com> 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 നോബിള് नोब्ळ् <no...@gmail.com>
>>>> To: solr-dev@lucene.apache.org
>>>> 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
>
Re: error: exceeded limit of maxWarmingSearcher
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
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 നോബിള് नोब्ळ्
<no...@gmail.com> 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
> <ot...@yahoo.com> 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 നോബിള് नोब्ळ् <no...@gmail.com>
>>> To: solr-dev@lucene.apache.org
>>> 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
Re: error: exceeded limit of maxWarmingSearcher
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
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
<ot...@yahoo.com> 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 നോബിള് नोब्ळ् <no...@gmail.com>
>> To: solr-dev@lucene.apache.org
>> 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
Re: error: exceeded limit of maxWarmingSearcher
Posted by Otis Gospodnetic <ot...@yahoo.com>.
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 നോബിള് नोब्ळ् <no...@gmail.com>
> To: solr-dev@lucene.apache.org
> 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
Re: error: exceeded limit of maxWarmingSearcher
Posted by Mark Miller <ma...@gmail.com>.
Noble Paul ??????? ?????? wrote:
> 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?
>
Likely committing too often somehow.
- Mark