lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luca Cavanna (Updated) (JIRA)" <>
Subject [jira] [Updated] (SOLR-3156) Check for locks on startup
Date Fri, 24 Feb 2012 15:06:48 GMT


Luca Cavanna updated SOLR-3156:

    Attachment: SOLR-3156.patch

Attached the first draft patch with a new test class. I've changed my mind a little bit and
put the check together with the unlockOnStartup code. There we already know if the index is
locked (IndexWriter#isLocked). If unlockOnStartup is enabled we remove the lock, otherwise
we throw a LockObtainFailedException, the same exception we would have seen at the first document
submission. What do you think guys? is this the right direction?
> Check for locks on startup
> --------------------------
>                 Key: SOLR-3156
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Luca Cavanna
>         Attachments: SOLR-3156.patch
> When using simple or native lockType and the application server is not shutdown properly
(kill -9), you don't notice problems until someone tries to add or delete a document. In fact,
you get errors every time Solr opens a new IndexWriter on the "locked" index. I'm aware of
the unlockOnStartup option, but I'd prefer to know and act properly when there's a lock, and
I think it would be better to know on startup, since Solr is not going to work properly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message