[
https://issues.apache.org/jira/browse/SOLR-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214959#comment-13214959
]
Luca Cavanna commented on SOLR-3156:
------------------------------------
I'd have a patch almost ready, but I'd like to hear your thoughts first of all.
I'd add a new check in the SolrCore#initIndex method. Would it be ok to try
opening a SolrIndexWriter and close it immediately? That way if there's a lock
and simple or native lockType, you'll immediately see an exception and Solr
won't start, instead of notice the problem only when the first document is
submitted. Should we add an option to the config for this check and make it
disabled by default?
Could you let me know what you think guys?
> 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]
