You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2010/08/11 00:35:21 UTC
[jira] Resolved: (LUCENE-2593) disk full can cause index corruption
in certain cases
[ https://issues.apache.org/jira/browse/LUCENE-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-2593.
----------------------------------------
Resolution: Fixed
> disk full can cause index corruption in certain cases
> -----------------------------------------------------
>
> Key: LUCENE-2593
> URL: https://issues.apache.org/jira/browse/LUCENE-2593
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>
> Attachments: LUCENE-2593.patch
>
>
> Robert uncovered this nasty bug, in adding more randomness to
> oal.index tests...
> I got a standalone test to show the issue; the corruption path is
> as follows:
> * The merge hits an initial exception (eg disk full when merging the
> postings).
> * In handling this exception, IW closes all the sub-readers,
> suppressing any further exceptions.
> * If one of these sub-readers has pending deletions, which happens
> if readers are pooled in IW, it will flush them. If that flush
> hits a 2nd exception (eg disk full), then SegmentReader
> [incorrectly] leaves the SegmentInfo's delGen advanced by 1,
> referencing a corrupt file, yet the SegmentReader is still
> forcefully closed.
> * If enough disk frees up such that a later IW.commit/close
> succeeds, the resulting segments file will reference an invalid
> deletions file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org