You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Jade Rubick <ja...@volunteersolutions.org> on 2007/09/13 00:07:26 UTC
Newbee seeks pointers for tracking down auto-warming error
Hi everyone:
We are getting very frequent errors of this nature in our jetty-stdout log:
SEVERE: Error during auto-warming of key:
org.apache.solr.search.QueryResultKey@def7992:java.lang.NullPointerException
at org.apache.lucene.search.FieldSortedHitQueue.<init>(
FieldSortedHitQueue.java:60)
at org.apache.solr.search.SolrIndexSearcher.sortDocSet(
SolrIndexSearcher.java:1053)
at org.apache.solr.search.SolrIndexSearcher.getDocListC(
SolrIndexSearcher.java:671)
at org.apache.solr.search.SolrIndexSearcher.access$100(
SolrIndexSearcher.java:56)
at org.apache.solr.search.SolrIndexSearcher$2.regenerateItem(
SolrIndexSearcher.java:242)
at org.apache.solr.search.LRUCache.warm(LRUCache.java:191)
at org.apache.solr.search.SolrIndexSearcher.warm(
SolrIndexSearcher.java:1138)
at org.apache.solr.core.SolrCore$1.call(SolrCore.java:412)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Any advice on how to track down this down?
I believe we are on SOLR 1.0 (that is what it says in build.xml). Solr
starts up with -Xms1200M -Xmx1700M
We do frequently updates and deletions, and commit every 30 minutes.
I found some references to similar issues:
http://www.nabble.com/Processor-load-tf3995401.html#a11421930
Here are the cache settings:
<!-- Cache used by SolrIndexSearcher for filters (DocSets),
unordered sets of *all* documents that match a query.
When a new searcher is opened, its caches may be prepopulated
or "autowarmed" using data from caches in the old searcher.
autowarmCount is the number of items to prepopulate. For LRUCache,
the autowarmed items will be the most recently accessed items. -->
<filterCache
class="solr.LRUCache"
size="32768"
initialSize="4096"
autowarmCount="4096"/>
<!-- queryResultCache caches results of searches - ordered lists of
document ids (DocList) based on a query, a sort, and the range
of documents requested. -->
<queryResultCache
class="solr.LRUCache"
size="32768"
initialSize="4096"
autowarmCount="4096"/>
<!-- documentCache caches Lucene Document objects (the stored fields for
each document).
Since Lucene internal document ids are transient, this cache will not
be autowarmed. -->
<!-- eWay - make this large to support our needs around faceted browsing
-->
<documentCache
class="solr.LRUCache"
size="131072"
initialSize="32768" />
Any help would be very appreciated.
Jade
--
Jade Rubick
Acting Chief Information Officer
United eWay
jade.rubick@uwa.unitedway.org
tel (503)285-4963
fax (707)671-1333
www.UNITEDeWAY.org
Re: Newbee seeks pointers for tracking down auto-warming error
Posted by Chris Hostetter <ho...@fucit.org>.
: We are getting very frequent errors of this nature in our jetty-stdout log:
:
: SEVERE: Error during auto-warming of key:
: org.apache.solr.search.QueryResultKey@def7992:java.lang.NullPointerException
: at org.apache.lucene.search.FieldSortedHitQueue.<init>(
: FieldSortedHitQueue.java:60)
: at org.apache.solr.search.SolrIndexSearcher.sortDocSet(
That's a weird one ... do they all say "Error during auto-warming of key"
or do you also see similar stack traces with different error messages (ie:
when doing regular requests, not just autowarming) ?
: I believe we are on SOLR 1.0 (that is what it says in build.xml). Solr
wow ... seriously? your build.xml says...
<!-- Solr version -->
<property name="version" value="1.0" />
...that's old. really old. predates the orriginal release old.
(1.1 was the first official apache release, 1.0 is just waht the build.xml
said when it was first commited becuase it had to say something ... even
before our first release w changed it to "1.1-dev" so you could tell the
difference between an official build and a build created by someone
checking out of subversion)
A lot has changed since then ... without a more concrete idea of how to
attempt to reproduce this, i'm not sure if anyone has the time/resources
to try and dig in and figure out what might be happening ... your best bet
is probably to upgrade to 1.2 and see if you still have problems.
-Hoss