Somehow today one of my indexes became corrupted.
I get the following IO exception when trying to open the index:
Exception in thread main java.io.IOException: read past EOF
at org.en.lucene.store.InputStream.refill(InputStream.java:154)
at
Hello,
Nobody has contributed a tool that verified index integrity, yet.
Is this the latest version of Lucene?
Are you hitting the 2GB/file limit?
Just some ideas.
Otis
--- H S [EMAIL PROTECTED] wrote:
Dear All,
We are experiencing a problem with
index updates. We have a fairly
large
Hinrich,
Can you please send a stack trace?
As others have mentioned, there isn't an index integrity checker.
Doug
P.S. Hi! How are you?
-Original Message-
From: H S [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 01, 2002 5:26 PM
To: [EMAIL PROTECTED]
Subject: corrupted index
Otis,
You can remove the .lock file and try re-indexing or continuing
indexing where you left off.
I am not sure about the corrupt index. I have never seen it happen,
and I believe I recall reading some messages from Doug Cutting saying
that index should never be left in an inconsistent
: corrupted index
Oh, I just thought of something (wine does body good).
Perhaps one could use Runtime (the class) to catch the JVM shutdown and
do whatever is needed to prevent index corruption. I believe there are
some shutdown hook methods in there that may let you do that. I'm too
lazy
Otis,
You can remove the .lock file and try re-indexing or continuing
indexing where you left off.
I am not sure about the corrupt index. I have never seen it happen,
and I believe I recall reading some messages from Doug Cutting saying
that index should never be left in an inconsistent
Oh, I just thought of something (wine does body good).
Perhaps one could use Runtime (the class) to catch the JVM shutdown and
do whatever is needed to prevent index corruption. I believe there are
some shutdown hook methods in there that may let you do that. I'm too
lazy to look up the API
