[ https://issues.apache.org/jira/browse/SOLR-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yonik Seeley reassigned SOLR-10115: ----------------------------------- Assignee: Yonik Seeley > Corruption in read-side of SOLR-HDFS stack > ------------------------------------------ > > Key: SOLR-10115 > URL: https://issues.apache.org/jira/browse/SOLR-10115 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Affects Versions: 4.4 > Reporter: Yonik Seeley > Assignee: Yonik Seeley > Attachments: YCS_HdfsTest.java > > > I've been trying to track down some random AIOOB exceptions in Lucene for a > customer, and I've managed to reproduce the issue with a unit test of > sufficient size in conjunction with highly concurrent read requests. > A typical stack trace looks like: > {code} > org.apache.solr.common.SolrException; > java.lang.ArrayIndexOutOfBoundsException: 172033655 > at org.apache.lucene.codecs.lucene40.BitVector.get(BitVector.java:149) > at > org.apache.lucene.codecs.lucene41.Lucene41PostingsReader$BlockDocsEnum.nextDoc(Lucene41PostingsReader.java:455) > at > org.apache.lucene.search.MultiTermQueryWrapperFilter.getDocIdSet(MultiTermQueryWrapperFilter.java:111) > at > org.apache.lucene.search.ConstantScoreQuery$ConstantWeight.scorer(ConstantScoreQuery.java:157) > {code} > The number of unique stack traces is relatively high, most AIOOB exceptions, > but some EOF. Most exceptions occur in the term index, however I believe > this may be just an artifact of where highly concurrent access is most likely > to occur. The queries that triggered this had many wildcards and other > multi-term queries. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org