[
https://issues.apache.org/jira/browse/SOLR-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Cavanna updated SOLR-3156:
-------------------------------
Attachment: SOLR-3156.patch
Hi Hoss,
thanks for your feedback.
{quote}
the one thing i might suggest is adding an ERROR log just before you throw the
exception (i'm in the "log early" team)
{quote}
I've added the log before throwing exception.
{quote}
trim those solrconfig files down so that they only contain the 5-6 minimum
lines they need inorder for the test to be meaningful
{quote}
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: https://issues.apache.org/jira/browse/SOLR-3156
> 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:
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]
