lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Dorsk (JIRA)" <>
Subject [jira] Created: (SOLR-2038) Corrupted Index After Commit
Date Wed, 11 Aug 2010 14:14:21 GMT
Corrupted Index After Commit

                 Key: SOLR-2038
             Project: Solr
          Issue Type: Bug
          Components: search, SearchComponents - other
    Affects Versions: 4.0
         Environment:   * solr-4.0, built on 2010-07-25 15:13:05Z
    * I'll post schema.xml and solrconfig.xml separately
  * java 1.6.0_18 (OpenJDK, IcedTea6 1.8, Ubuntu 9.10)
  * Drupal 6.17
  * Drupal Apache Solr Search Integration, built on 2010/07/25 16:16:46
            Reporter: Alexander Dorsk

If I run queries which have matches after I commit documents, I get IndexOutOfBounds exceptions.

This is repeatable.

==== Details ====

=== Stack Trace ===

Problem accessing /solr/select. Reason:

    Index: 114, Size: 36

java.lang.IndexOutOfBoundsException: Index: 114, Size: 36
	at java.util.ArrayList.rangeCheck(
	at java.util.ArrayList.get(
	at org.apache.lucene.index.FieldInfos.fieldInfo(
	at org.apache.lucene.index.FieldsReader.doc(
	at org.apache.lucene.index.SegmentReader.document(
	at org.apache.lucene.index.DirectoryReader.document(
	at org.apache.solr.util.SolrPluginUtils.optimizePreFetchDocs(
	at org.apache.solr.handler.component.QueryComponent.doPrefetch(
	at org.apache.solr.handler.component.QueryComponent.process(
	at org.apache.solr.handler.component.SearchHandler.handleRequestBody(
	at org.apache.solr.handler.RequestHandlerBase.handleRequest(
	at org.apache.solr.core.SolrCore.execute(
	at org.apache.solr.servlet.SolrDispatchFilter.execute(
	at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
	at org.mortbay.jetty.servlet.ServletHandler.handle(
	at org.mortbay.jetty.servlet.SessionHandler.handle(
	at org.mortbay.jetty.handler.ContextHandler.handle(
	at org.mortbay.jetty.webapp.WebAppContext.handle(
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
	at org.mortbay.jetty.handler.HandlerCollection.handle(
	at org.mortbay.jetty.handler.HandlerWrapper.handle(
	at org.mortbay.jetty.Server.handle(
	at org.mortbay.jetty.HttpConnection.handleRequest(
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
	at org.mortbay.jetty.HttpParser.parseNext(
	at org.mortbay.jetty.HttpParser.parseAvailable(
	at org.mortbay.jetty.HttpConnection.handle(
	at org.mortbay.thread.QueuedThreadPool$
=== Procedure ===

Here is how I make it happen:
  * create a new cck node with some custom fields
  * run drupal's cron
  * run a solr query that should have results.
  * error message above appears.

For example, I have a cck type 'authorized term', that has all text fields.  I make a new
'authorized term' and run Drupal's cron.  Then I execute this query:


(there should be a result for this query)

The stack trace above appears as the result.

Note that if there are no results (e.g. http://localhost:8983/solr/select?q=asdfadf) then
there is no error.

If I delete the index and rebuild it, and then run the query, there are no errors and I get
the results I expect.

=== related ===
might be related to this message?

I'm using solr-4.0 because of the lucene syntax query parsing (I need fuzzy searches).

If you need any other diagnostic info, just let me know.  I'm fairly new to Solr, so my apologies
if I'm missing anything.  

I think you all are doing great work on the project, and Solr has already been a tremendous
help to me.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message