[
https://issues.apache.org/jira/browse/SOLR-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215538#comment-13215538
]
Martijn van Groningen edited comment on SOLR-3156 at 2/24/12 10:46 AM:
-----------------------------------------------------------------------
I also prefer to know that the index is locked at startup than when the first
document is added!
Opening and then closing a SolrIndexWriter seems like the most easy way to
check this in the SolrCore#initIndex method.
was (Author: martijn.v.groningen):
I also prefer to know that the index is locked at startup than when the
first document is added!
Opening and then closing a SolrIndexReader seems like the most easy way to
check this in the SolrCore#initIndex method.
> Check for locks on startup
> --------------------------
>
> Key: SOLR-3156
> URL: https://issues.apache.org/jira/browse/SOLR-3156
> Project: Solr
> Issue Type: Improvement
> Reporter: Luca Cavanna
>
> 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:
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: [email protected]
For additional commands, e-mail: [email protected]
