lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-555) Index Corruption
Date Sat, 28 Oct 2006 00:02:17 GMT
    [ ] 
Michael McCandless commented on LUCENE-555:

Just copying this off the dev list -- there is indeed at least one place where if a writer
crashes it can leave the index unloadable.  I will open a new issue on this.

Tero, by any chance are you using addIndexes?

Ning Li says:

Lucene could produce an inconsistent index if addIndexes(Directory[])
does not run to its completion. The following is my recent comment on
another issue.

"This makes me notice a bug in current addIndexes(Directory[]). In
current addIndexes(Directory[]), segment infos in S are added to T's
"segmentInfos" upfront. Then segments in S are merged to T several at
a time. Every merge is committed with T's "segmentInfos". So if a
reader is opened on T while addIndexes(Directory[]) is going on, it
could see an inconsistent index."

> Index Corruption
> ----------------
>                 Key: LUCENE-555
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 1.9
>         Environment: Linux FC4, Java 1.4.9
>            Reporter: dan
>            Priority: Critical
> Index Corruption
> >>>>>>>>> output
> ../_aki.fnm (No such file or directory)
>         at Method)
>         at<init>(
>         at$Descriptor.<init>(
>         at<init>(
>         at
>         at org.apache.lucene.index.FieldInfos.<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.IndexWriter.mergeSegments(
>         at org.apache.lucene.index.IndexWriter.mergeSegments(
>         at org.apache.lucene.index.IndexWriter.optimize(
> >>>>>>>>> input
> - I open an index, I read, I write, I optimize, and eventually the above happens. The
index is unusable.
> - This has happened to me somewhere between 20 and 30 times now - on indexes of different
shapes and sizes.
> - I don't know the reason. But, the following requirement applies regardless.
> >>>>>>>>> requirement
> - Like all modern database programs, there has to be a way to repair an index. Period.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


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

View raw message