[ 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 Attached the first draft patch with a new test class. I've changed my mind a little bit and put the check together with the unlockOnStartup code. There we already know if the index is locked (IndexWriter#isLocked). If unlockOnStartup is enabled we remove the lock, otherwise we throw a LockObtainFailedException, the same exception we would have seen at the first document submission. What do you think guys? is this the right direction? > 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 > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org