lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tero Hagström (JIRA) <j...@apache.org>
Subject [jira] Commented: (LUCENE-555) Index Corruption
Date Thu, 26 Oct 2006 08:11:17 GMT
    [ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12444827 ] 
            
Tero Hagström commented on LUCENE-555:
--------------------------------------

We've experienced Lucene index corruption a few times on a production system. What makes it
tricky is, that 1) the ability to search the Lucene index is critical in that system, and
2) recreating it takes rather long. Thus the index corruption renders the system unusable
for a long period.

The latest index corruption appears to have resulted from a disk partition being full. I would
expect that Lucene would fail gracefully in that situation and not corrupt it's index.

Any chance of reopening this issue?




> Index Corruption
> ----------------
>
>                 Key: LUCENE-555
>                 URL: http://issues.apache.org/jira/browse/LUCENE-555
>             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
> java.io.FileNotFoundException: ../_aki.fnm (No such file or directory)
>         at java.io.RandomAccessFile.open(Native Method)
>         at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
>         at org.apache.lucene.store.FSIndexInput$Descriptor.<init>(FSDirectory.java:425)
>         at org.apache.lucene.store.FSIndexInput.<init>(FSDirectory.java:434)
>         at org.apache.lucene.store.FSDirectory.openInput(FSDirectory.java:324)
>         at org.apache.lucene.index.FieldInfos.<init>(FieldInfos.java:56)
>         at org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:144)
>         at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:129)
>         at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:110)
>         at org.apache.lucene.index.IndexWriter.mergeSegments(IndexWriter.java:674)
>         at org.apache.lucene.index.IndexWriter.mergeSegments(IndexWriter.java:658)
>         at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:517)
> >>>>>>>>> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message