lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Assigned] (SOLR-10115) Corruption in read-side of SOLR-HDFS stack
Date Wed, 22 Feb 2017 01:16:44 GMT


Yonik Seeley reassigned SOLR-10115:

    Assignee: Yonik Seeley

> Corruption in read-side of SOLR-HDFS stack
> ------------------------------------------
>                 Key: SOLR-10115
>                 URL:
>             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:
> 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(
>         at org.apache.lucene.codecs.lucene41.Lucene41PostingsReader$BlockDocsEnum.nextDoc(
>         at
>         at$ConstantWeight.scorer(
> {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

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

View raw message