:
: Yesterday's error log contains something peculiar:
:
: ERROR [solr.search.SolrCache] - [pool-29-thread-1] - : Error during auto-
: warming of key:+*:*
:
(1.0/(7.71E-8*float(ms(const(1298682616680),date(sort_date)))+1.0))^20.0:java.lang.NullPointerException
: at org.apache.lucene.util.StringHelper.intern(StringHelper.java:36)
: at
: org.apache.lucene.search.FieldCacheImpl$Entry.<init>(FieldCacheImpl.java:275)
: at
: org.apache.lucene.search.FieldCacheImpl.getLongs(FieldCacheImpl.java:525)
: at
:
org.apache.solr.search.function.LongFieldSource.getValues(LongFieldSource.java:57)
: at
:
org.apache.solr.search.function.DualFloatFunction.getValues(DualFloatFunction.java:48)
: at
:
org.apache.solr.search.function.ReciprocalFloatFunction.getValues(ReciprocalFloatFunction.java:61)
that is odd...
can you let us know exactly what verison of Solr/Lucne you are using (if
it's not an official release, can you let us know exactly what the version
details on the admin info page say, i'm curious about the svn revision)
can you also please let us know what types of queries you are generating?
... that's the toString output of a query and it's not entirely clear what
the original looked like. If you can recognize what the original query
was, it would also be helpful to know if you can consistently reproduce
this error on autowarming after executing that query (or queries like it
with a slightly differnet date value)
One of the things that particularly boggles me is this...
: org.apache.solr.search.SolrIndexSearcher.getDocSet(SolrIndexSearcher.java:545)
: at
:
org.apache.solr.search.SolrIndexSearcher.cacheDocSet(SolrIndexSearcher.java:520)
[...]
: Well, i use Dismax' bf parameter to boost very recent documents. I'm not
using
: the queryResultCache or documentCache, only filterCache and Lucene
fieldCache.
... that cache warming stack trace seems to be coming from filterCache,
but that contradicts your statement that you don't use the filterCache.
independent of your comments, that's an odd looking query to be cached in
the filter cache anyway, since it includes a mandatory matchalldocs
clause, and seems to only exist for boosting on that function.
-Hoss
