lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ning Li (JIRA)" <>
Subject [jira] Commented: (LUCENE-702) Disk full during addIndexes(Directory[]) can corrupt index
Date Tue, 12 Dec 2006 20:02:22 GMT
    [ ] 
Ning Li commented on LUCENE-702:

> This is actually intentional: I don't want to write to the same
> segments_N filename, ever, on the possibility that a reader may be
> reading it.  Admittedly, this should be quite rare (filling up disk
> and then experiencing contention, only on Windows), but still I wanted
> to keep "write once" even in this case.

In IndexWriter, the rollbackTransaction call in commitTransaction could
cause write to the same segment_N filename, right?

The "write once" semantics is not kept for segment names or .delN. This
is ok because no reader will read the old versions.

> Disk full during addIndexes(Directory[]) can corrupt index
> ----------------------------------------------------------
>                 Key: LUCENE-702
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.1
>            Reporter: Michael McCandless
>         Assigned To: Michael McCandless
>         Attachments: LUCENE-702.patch, LUCENE-702.take2.patch
> This is a spinoff of LUCENE-555
> If the disk fills up during this call then the committed segments file can reference
segments that were not written.  Then the whole index becomes unusable.
> Does anyone know of any other cases where disk full could corrupt the index?
> I think disk full should worse lose the documents that were "in flight" at the time.
 It shouldn't corrupt the index.

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