lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhang, Lisheng" <>
Subject RE: lucene Indexer failed to close, but later indexing still OK?
Date Tue, 07 Aug 2012 00:34:34 GMT

Since last time I reported the issue below, I had a few similar issue, like at one
time when I ran CheckIndex, I got error like some delete file not found, but after
a few seconds CheckIndex is 100% OK.

Is this a problem only happening in 2.3.2 but fixed in later release (sometimes data
is corrupted but later healed itself)?

Thanks very much for helps, Lisheng

-----Original Message-----
From: Zhang, Lisheng []
Sent: Thursday, August 02, 2012 10:56 AM
Subject: lucene Indexer failed to close, but later indexing still OK?

We are using lucene 2.3.2 on linux/ubuntu (we will upgrade lucene soon), recently we got exception:
read past EOF read past EOF
at org.apache.lucene.index.CompoundFileReader$CSIndexInput.readInternal(
at 63)
at org.apache.lucene.index.SegmentTermEnum.scanTo(
at org.apache.lucene.index.TermInfosReader.scanEnum(
at org.apache.lucene.index.TermInfosReader.get(
at org.apache.lucene.index.IndexReader.termDocs(
at org.apache.lucene.index.IndexReader.deleteDocuments(
at org.apache.lucene.index.IndexWriter.applyDeletes(
This happened when we tried to commit the change. But later we ran the CheckIndex, there is
no error
at all and we can still index without problem. 
Is this a know issue (I searched Google, it is said if applying 4.0 to old index data we may
encounter this
error, but we all use lucene 2.3.2)?
Thanks very much for helps!

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

View raw message