Re: Solr Search Error

[vivek sar <vi...@gmail.com>]

Hi,

  I'm using the Solr 1.4 (03/29 nightly build) and when searching on a
large index (40G) I get the same exception as in this thread,

 HTTP Status 500 - 13724 java.lang.ArrayIndexOutOfBoundsException:
13724 at org.apache.lucene.search.TermScorer.score(TermScorer.java:74)
at org.apache.lucene.search.TermScorer.score(TermScorer.java:61) at
org.apache.lucene.search.IndexSearcher.doSearch(IndexSearcher.java:262)
at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:250)
at org.apache.lucene.search.Searcher.search(Searcher.java:126) at
org.apache.lucene.search.Searcher.search(Searcher.java:105) at
org.apache.solr.search.SolrIndexSearcher.getDocListNC(SolrIndexSearcher.java:1072)
at
...

The search url  is,

http://think2.co.com:8080/solr/20090415_1/select/?q=japan&version=2.2&start=0&rows=10&indent=on

It would have millions of records matching this term, but I guess that
shouldn't throw this exception. I saw a similar jira to
ArrayOutOfBoundException,
https://issues.apache.org/jira/browse/SOLR-450  (it's not the same
though).

I also see someone reported this same problem back in 2007 so I'm not
sure whether it's a real bug or some configuration issue,

http://www.nabble.com/ArrayIndexOutOfBoundsException-on-TermScorer-td11750899.html#a11750899

Any ideas?

Thanks,
-vivek



On Fri, Mar 27, 2009 at 10:11 AM, Narayanan, Karthikeyan
<Ka...@gs.com> wrote:
> Hi Otis,
>              Thanks for the  recommendation. Will try with latest
> nightly build.. I  did couple of full data import and got this error at
> few times while searching..
>
>
> Thanks.
>
> Karthik
>
>
> -----Original Message-----
> From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> Sent: Friday, March 27, 2009 12:57 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr Search Error
>
>
> Hi Karthik,
>
> First thing I'd do is get the latest Solr nightly build.
> If that doesn't fix thing, I'd grab the latest Lucene nightly build and
> use it to replace Lucene jars that are in your version of Solr.
> If that doesn't work I'd email the ML with a bit more info about the
> type of search that causes this (e.g. Do all searches cause this or only
> some?  What do those that trigger this error look like or have in
> common?)
>
> Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
>
>
> ----- Original Message ----
>> From: "Narayanan, Karthikeyan" <Ka...@gs.com>
>> To: solr-user@lucene.apache.org
>> Sent: Friday, March 27, 2009 11:42:12 AM
>> Subject: Solr Search Error
>>
>> Hi All,
>>            I am intermittently getting this Exception when I do the
> search.
>> What could be the reason?.
>>
>> Caused by: org.apache.solr.common.SolrException: 11938
>> java.lang.ArrayIndexOutOfBoundsException: 11938         at
>> org.apache.lucene.search.TermScorer.score(TermScorer.java:74)
> at
>> org.apache.lucene.search.TermScorer.score(TermScorer.java:61)
> at
>> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:137)
> at
>> org.apache.lucene.search.Searcher.search(Searcher.java:126)  at
>> org.apache.lucene.search.Searcher.search(Searcher.java:105)  at
>>
> org.apache.solr.search.SolrIndexSearcher.getDocListNC(SolrIndexSearcher.
> java:966)
>>   at
>>
> org.apache.solr.search.SolrIndexSearcher.getDocListC(SolrIndexSearcher.j
> ava:838)
>>    at
>>
> org.apache.solr.search.SolrIndexSearcher.search(SolrIndexSearcher.java:2
> 69)  at
>>
> org.apache.solr.handler.component.QueryComponent.process(QueryComponent.
> java:160)
>>   at
>>
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(Search
> Handler.java:169)
>>   at
>>
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerB
> ase.java:131)
>>       at org.apache.solr.core.SolrCore.execute(SolrCore.java:1204)
> at
>>
> org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.ja
> va:303)
>>     at
>>
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.j
> ava:232)
>>    at
>>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> tionFilterChain.java:215)
>>   at
>>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> erChain.java:188)
>>   at
>>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
> e.java:210)
>> at
>>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
> e.java:174)
>> at
>>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator
> Base.java:433)
>>      at
>>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
> :127)
>>     at
>>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
> :117)
>>     at
>>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
> java:108)
>>   at
>>
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
> 51)  at
>>
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:87
> 0)   at
>>
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc
> essConnection(Http11BaseProtocol.java:665)
>> at
>>
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
> .java:528)
>> at
>>
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow
> erWorkerThread.java:81)
>>     at
>>
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
> .java:685)
>> at java.lang.Thread.run(Thread.java:619)
>>
>>
>> Thanks.
>>
>> Karthik
>

Re: Solr Search Error

[Chris Hostetter <ho...@fucit.org>]

:  HTTP Status 500 - 13724 java.lang.ArrayIndexOutOfBoundsException:
: 13724 at org.apache.lucene.search.TermScorer.score(TermScorer.java:74)

An ArrayIndexOutOfBoundsException from TermScorer is a prtty serious error 
-- and probably indicates an interal problem of some kind, not a config 
issue or user error.

If i remember correctly, the only times i've ever seen errors like this 
were either:

1) corrupt indexe ... either the machine or this disk or Solr had a hard 
crash (OOM in the case of Solr) ... using the CheckIndex tool would 
probably point out hte problem.

2) hardware glitch ... bad ram or bad disk

3) bug in Lucene ... which is possible if you're using trunk, there have 
been a lot of little performance tweaks recently.  if you can reporduce 
this type of problem regularly sharing your configs and info about how you 
build your index can probably help people track down the problem.



-Hoss