On Tue, Feb 9, 2010 at 2:56 PM, Tom Burton-West wrote:
> I'm not sure I understand. CheckIndex reported a negative number:
> -16777214.
Right, we are overflowing the positive ints, which wraps around to the
smallest int (-2.1 billion), and then dividing by 128 = ~ -1677214.
Lucene has an array
exception.
>
> Hmm -- can you try a patched Lucene in your area? I have one small
> change to try that may increase the limit to termIndexInterval
> (default 128) * 2.1 billion.
>
> Mike
>
>
> --
> View this message in context:
> http://old.nabble.com/TermInfosR
e.com/TermInfosReader.get-ArrayIndexOutOfBoundsException-tp27506243p2752.html
Sent from the Solr - User mailing list archive at Nabble.com.
>> test: stored fields...OK [3550 total field count; avg 4.856 fields
>> per doc]
>> test: term vectorsOK [0 total vector count; avg 0 term/freq
>> vector fields per doc]
>>
>> WARNING: 1 broken segments (containing 554615 documents) detected
>> WARNING: would write new segments file, and 554615 documents would be lost,
>> if -fix were specified
>>
>>
>> [tburt...@slurm-4 ~]$
>>
>>
>> The index is corrupted. In some places ArrayIndex and NPE are not
>> wrapped as CorruptIndexException.
>>
>> Try running your code with the Lucene assertions on. Add this to the
>> JVM arguments: -ea:org.apache.lucene...
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/TermInfosReader.get-ArrayIndexOutOfBoundsException-tp27506243p27518800.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
ecified
>
>
> [tburt...@slurm-4 ~]$
>
>
> The index is corrupted. In some places ArrayIndex and NPE are not
> wrapped as CorruptIndexException.
>
> Try running your code with the Lucene assertions on. Add this to the
> JVM arguments: -ea:org.apache.lucene...
>
>
> --
> View this message in context:
> http://old.nabble.com/TermInfosReader.get-ArrayIndexOutOfBoundsException-tp27506243p27518800.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
ns on. Add this to the
JVM arguments: -ea:org.apache.lucene...
--
View this message in context:
http://old.nabble.com/TermInfosReader.get-ArrayIndexOutOfBoundsException-tp27506243p27518800.html
Sent from the Solr - User mailing list archive at Nabble.com.
Which version of Solr/Lucene are you using?
Can you run Lucene's CheckIndex tool (java -ea:org.apache.lucene
org.apache.lucene.index.CheckIndex /path/to/index) and then post the
output?
Have you altered any of IndexWriter's defaults (via solrconfig.xml)?
Eg the termIndexInterval?
Mike
On Mon, F
The index is corrupted. In some places ArrayIndex and NPE are not
wrapped as CorruptIndexException.
Try running your code with the Lucene assertions on. Add this to the
JVM arguments: -ea:org.apache.lucene...
On Mon, Feb 8, 2010 at 1:02 PM, Burton-West, Tom wrote:
> Hello all,
>
> After optimiz
Hello all,
After optimizing rather large indexes on 10 shards (each index holds about
500,000 documents and is about 270-300 GB in size) we started getting
intermittent TermInfosReader.get() ArrayIndexOutOfBounds exceptions. The
exceptions sometimes seem to occur on all 10 shards at the sam
