lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael van Rooyen <>
Subject read past EOF since migration to 2.9.1
Date Wed, 17 Feb 2010 14:18:05 GMT
Hello all!

We've been using Lucene for a few years and it's worked without a 
murmur.  I recently upgraded from version 2.3.2 to 2.9.1.  We didn't 
need to make any code changes for the upgrade - apart from the 
deprecation warnings, the code compiled cleanly and 2.9.1 worked fine in 

Since going live a few days ago, however, we've twice had read past EOF 
exceptions.  The first time it happened, I checked the index and an 
error had crept into the deleted docs count on the main segment:

Segments file=segments_cefg numSegments=4 version=FORMAT_DIAGNOSTICS 
[Lucene 2.9]
   1 of 4: name=_abtf8 docCount=9710072
     size (MB)=4,254.56
     has deletions [delFileName=_abtf8_df.del]
     test: open reader.........FAILED
     WARNING: fixIndex() would remove reference to this segment; full 
java.lang.RuntimeException: delete count mismatch: info=263213 vs 
         at org.apache.lucene.index.CheckIndex.main(

I checked the logs for the our process that updates the index and there 
were no exceptions logged.  I then optimized the index and checked it 
again and it was all okay, so obviously the optimize / merge process is 
happy to work on an index where the deletions file is in error.

Today, we got the second read past EOF exception.  This time I checked 
the index again and no errors were detected.  I think that whatever 
error there was that led to the EOF exception was on a small segment 
file that got merged into a larger one as more updates were made, before 
I had time to check the index.

Does anyone have any ideas as to what could cause this, or what we could 
do to avoid it happening?  The stack trace for the EOF exception is below.


Caused by: read past EOF

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

View raw message