lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless" <>
Subject Re: Help with Lucene Indexer crash recovery
Date Fri, 05 Oct 2007 11:51:52 GMT
"vivek sar" <> wrote:

> We are using Lucene 2.3.

Do you mean Lucene 2.2?  Your stack trace seems to line up with 2.2,
and 2.3 isn't quite released yet.

> The problem we are facing is quite a few times if our application is
> stopped (killed or crash) while Indexer is doing its job, the next
> time when we bring up the application the Indexer fails to run with
> the following exception,

> 2007-10-04 12:29:53,089 ERROR [PS thread 10] IndexerJob - Full-text
> indexer failed to index
> /opt/manager/apps/conf/index/MasterIndex/_llb.cfs (No such file or
> directory)
>         at Method)
>         at<init>(Unknown Source)
>         at
>         at
>         at
>         at
>         org.apache.lucene.index.CompoundFileReader.<init>(
>         at
>         org.apache.lucene.index.SegmentReader.initialize(
>         at
>         org.apache.lucene.index.SegmentReader.get(
>         at
>         org.apache.lucene.index.SegmentReader.get(
>         at
>         org.apache.lucene.index.IndexReader$1.doBody(
>         at
>         org.apache.lucene.index.SegmentInfos$
> The search also doesn't work after this.

Can you share some details of how you are using Lucene, and, how/why
it's killed or crashed so often?  When it crashes, do you get an
exception from Lucene (which could be the root cause here)?

What OS and filesystem is the index on?  Are you changing any default
settings like autoCommit, lock factory & lock file location, etc?

Even if Lucene (JVM) is killed, the index should not become corrupt in
this particular way, unless the IO system fails to complete its
"write" operations.  Lucene always writes & closes new segments files
(_llb.cfs) before writing the segments_N file that refers to them.

> Looks like the index were left in some weird state (might be
> corrupted). I was wondering if there is a tool or a way to repair the
> indexes if we are not able to open them at run-time?

I just took a first stab at just such a tool, here:

Please be very very careful!: I just wrote this code and it could have
some horrible bug that destroys your index.  So make a backup of your
index first.

Could you first run that tool without the "-fix" option and post back
the resulting output?


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

View raw message