lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <apa...@elyograg.org>
Subject Re: Error opening new searcher
Date Fri, 20 May 2016 09:40:19 GMT
On 5/20/2016 1:46 AM, Victor D'agostino wrote:
> What doest this "try again later" log means in solr-xxxx-console.log :

You should really disable console logging entirely.  I assume you're
running at least version 5.0?

> 193899678 WARN  (qtp1393423910-18329) [c:db s:shard3 r:core_node3
> x:db_shard3_replica1] o.a.s.u.p.DistributedUpdateProcessor Error
> sending update to http://10.69.212.22:8983/solr
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:
> Error from server at http://10.69.212.22:8983/solr/db_shard3_replica1:
> Error opening new searcher. exceeded limit of maxWarmingSearchers=2,
> try again later.
>
> Am I supposed to resend the document or will it be inserted just fine
> later ?

Most likely the update itself was fine -- the error was when opening a
new searcher, which is something that happens at commit time.  You would
need to check the solr.log file on the server with address 10.69.212.22
to be sure.  This particular error message means that you are committing
too frequently -- two previous commits with openSearcher=true were not
yet finished before a third commit with openSearcher=true was started.

> And is it possible to set the log timestamp "193899678" to a human
> readable format ?

Check the timestamp in the solr.log file.  Like I said above -- the
console log should be disabled entirely.  You should be able to remove
it as a logging destination by editing resources/log4j.properties
(assuming 5.x or 6.x).

Thanks,
Shawn


Mime
View raw message