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 Tue, 28 Feb 2012 09:47:48 GMT


Luca Cavanna updated SOLR-3156:

    Attachment: SOLR-3156.patch

Hi Hoss, 
thanks for your feedback.

the one thing i might suggest is adding an ERROR log just before you throw the exception (i'm
in the "log early" team)
I've added the log before throwing exception.

trim those solrconfig files down so that they only contain the 5-6 minimum lines they need
inorder for the test to be meaningful
I completely agree, I already did a little, but I just did it (a lot) more. You'll like it
now. :)
> Check for locks on startup
> --------------------------
>                 Key: SOLR-3156
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Luca Cavanna
>         Attachments: SOLR-3156.patch, 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