lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dan (JIRA)" <>
Subject [jira] Created: (LUCENE-555) Index Corruption
Date Mon, 24 Apr 2006 06:50:07 GMT
Index Corruption

         Key: LUCENE-555
     Project: Lucene - Java
        Type: Bug

  Components: Index  
    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 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