lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (LUCENE-748) Exception during IndexWriter.close() prevents release of the write.lock
Date Mon, 18 Dec 2006 22:23:22 GMT
    [ ] 
Hoss Man commented on LUCENE-748:

given the changes made in LUCENE-702, i concur with your assesment Michael: keeping the lock
open so that the caller can attempt to deal with the problem then retry makes sense.

even if we decided that the consistent state of the IndexWriter isn't an invarient that the
user can rely on, asking users to forcably unlock in the event of an exception on close seems
like a more reasonable expectation then to forcably unlock for them automatically.

> Exception during IndexWriter.close() prevents release of the write.lock
> -----------------------------------------------------------------------
>                 Key: LUCENE-748
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 1.9
>         Environment: Lucene 1.4 through 2.1 HEAD (as of 2006-12-14)
>            Reporter: Jed Wesley-Smith
> After encountering a case of index corruption - see
- when the close() method encounters an exception in the flushRamSegments() method, the index
write.lock is not released (ie. it is not really closed).
> The writelock is only released when the IndexWriter is GC'd and finalize() is called.

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