lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3156) Check for locks on startup
Date Tue, 28 Feb 2012 06:04:49 GMT


Hoss Man commented on SOLR-3156:

Luca: the change to SolrCore looks good to me ... the one thing i might suggest is adding
an ERROR log just before you throw the exception (i'm in the "log early" team)

The test looks awesome, but *PLEASE* trim those solrconfig files down so that they only contain
the 5-6 minimum lines they need inorder for the test to be meaningful ... we have far too
many big bloated test configs already, the goal is to stop adding new ones and make sure each
test config has a specific and easy to see purpose.
> 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