You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2013/05/30 17:31:20 UTC

[jira] [Commented] (LUCENE-5024) Can we reliably detect an incomplete first commit vs index corruption?

    [ https://issues.apache.org/jira/browse/LUCENE-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670410#comment-13670410 ] 

Robert Muir commented on LUCENE-5024:
-------------------------------------

even if we can, i'm not sure we should.

real users hit corruption issues too. sorry to the two java-users for the inconvenience, but corruption/dataloss is WAY worse.
                
> Can we reliably detect an incomplete first commit vs index corruption?
> ----------------------------------------------------------------------
>
>                 Key: LUCENE-5024
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5024
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index
>            Reporter: Michael McCandless
>             Fix For: 5.0, 4.4
>
>
> Normally, if something bad happens (OS, JVM, hardware crashes) while
> IndexWriter is committing, we will just fallback to the prior commit
> and no intervention necessary from the app.
> But if that commit is the first commit, then on restart IndexWriter
> will now throw CorruptIndexException, as of LUCENE-4738.
> Prior to LUCENE-4738, in LUCENE-2812, we used to try to detect the
> corrupt first commit, but that logic was dangerous and could result in
> falsely believing no index is present when one is, e.g. when transient
> IOExceptions are thrown due to file descriptor exhaustion.
> But now two users have hit this change ... see "CorruptIndexException
> when opening Index during first commit" and "Calling
> IndexWriter.commit() immediately after creating the writer", both on
> java-user.
> It would be nice to get back to not marking an incomplete first commit
> as corruption ... but we have to proceed carefully.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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