IndexOutOfBoundsException after disk full on replication
--------------------------------------------------------

                 Key: SOLR-3023
                 URL: https://issues.apache.org/jira/browse/SOLR-3023
             Project: Solr
          Issue Type: Bug
          Components: replication (java)
    Affects Versions: 3.5
         Environment: EC2 instance running Ubuntu 10.04; Solr installed on a 
15GB EBS volume 
            Reporter: Matt DeBoard


I am running Solr 3.5 with a master/slave configuration. Master instance 
handles indexing; slave handles queries. I was investigating why changes to 
schema.xml were not propogating to production servers (specifically, 
implementing index-time synonyms) and saw that my EBS volume was full (15GB). 
After freeing some space by deleting an old Solr 3.4 installation that was no 
longer being used, I began seeing the following errors from the slave:

Jan 10, 2012 6:57:33 PM org.apache.solr.common.SolrException log
SEVERE: java.lang.IndexOutOfBoundsException: Index: 108, Size: 40
        at java.util.ArrayList.RangeCheck(ArrayList.java:547)
        at java.util.ArrayList.get(ArrayList.java:322)
        at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:299)
        at org.apache.lucene.index.FieldsReader.doc(FieldsReader.java:238)
        at 
org.apache.lucene.index.SegmentReader.document(SegmentReader.java:477)
        at 
org.apache.lucene.index.DirectoryReader.document(DirectoryReader.java:583)
        at 
org.apache.solr.search.SolrIndexReader.document(SolrIndexReader.java:260)
        at 
org.apache.solr.search.SolrIndexSearcher.doc(SolrIndexSearcher.java:452)
        at 
org.apache.solr.util.SolrPluginUtils.optimizePreFetchDocs(SolrPluginUtils.java:271)
        at 
org.apache.solr.handler.component.QueryComponent.doPrefetch(QueryComponent.java:478)
        at 
org.apache.solr.handler.component.QueryComponent.process(QueryComponent.java:385)
        at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:194)
        at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:1372)
        at 
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:356)
        at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:252)
        at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
        at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
        at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
        at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
        at 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at 
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
        at 
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

This was happening inconsistently. That is, some queries would be handled, some 
would not. For instance, the page at http://att-veterans.jobs would NOT render, 
but e.g. http://lockheedmartin.jobs would. Restarting the Jetty server did not 
alleviate the problem. I diverted all queries to my master instance, which ran 
fine with no errors.

Ultimately I solved the issue by deleting the index files and replicating, then 
put the slave back into service.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to