[jira] [Commented] (LUCENE-3660) If indexwriter hits a non-ioexception from indexExists it leaks a write.lock

["Michael McCandless (Commented) (JIRA)" <ji...@apache.org>]

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

Michael McCandless commented on LUCENE-3660:
--------------------------------------------

+1, good catch!
                
> If indexwriter hits a non-ioexception from indexExists it leaks a write.lock
> ----------------------------------------------------------------------------
>
>                 Key: LUCENE-3660
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3660
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>         Attachments: LUCENE-3660.patch
>
>
> the rest of IW's ctor is careful about this.
> IndexReader.indexExists catches any IOException and returns false, but the problem
> occurs if some other exception (in my test, UnsupportedOperationException, but you
> can imagine others are possible), when trying to e.g. read in the segments file.
> I think we just need to move the IR.exists stuff inside the try / finally

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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