After investigating more, here is the tomcat log herebelow. It is
indeed the same problem: exceeded limit of maxWarmingSearchers=2,.
could not be solr able to close oldest warming searcher and replace it
by new one?
On Tue, Sep 11, 2012 at 10:52 AM, Radim Kolar h...@filez.com wrote:
After investigating more, here is the tomcat log herebelow. It is indeed
the same problem: exceeded limit of maxWarmingSearchers=2,.
could not be solr able to close oldest warming searcher and replace it by
new one?
That
could not be solr able to close oldest warming searcher and replace it by
new one?
That approach can easily lead to starvation (i.e. you never get a new
searcher usable for queries).
It will not. If there is more then 1 warming searcher. Look at this schema:
1. current in use searcher
2. 1st
Hoss,
After investigating more, here is the tomcat log herebelow. It is indeed
the same problem: exceeded limit of maxWarmingSearchers=2,.
It is an indexing box and the comment says that we could rise this number
to 4 or something. I can do that but I have four questions though:
- is it
Hello,
Using package org.apache.solr.client.solrj;
when I do:
UpdateResponse ur = solrServer.commit(false, false);
I get sometimes (not often):
SolrException e where e.code() ==
SolrException.ErrorCode.SERVICE_UNAVAILABLE.code
When I catch this exception, I try to commit again, the call
: I get sometimes (not often):
: SolrException e where e.code() ==
: SolrException.ErrorCode.SERVICE_UNAVAILABLE.code
Are there any errors in your solr server logs?
Are you using the DistributedUpdateProcessor (ie: SolrCloud) ?
There aren't many places in Solr that will throw a 503 status
yet.
Restarting the node fixed the trouble.
-Original message-
From:Chris Hostetter hossman_luc...@fucit.org
Sent: Fri 07-Sep-2012 23:02
To: solr-user@lucene.apache.org
Subject: Re: [Solr4 beta] error 503 on commit
: I get sometimes (not often):
: SolrException e where e.code
