We have a very active large index running a solr trunk from a few
weeks ago that has been going down about once a week for this:
[11:08:17.149] No lockType configured for /home/bwhitman/XXX/XXX/
discovered-solr/data/index assuming 'simple'
[11:08:17.150] org.apache.lucene.store.LockObtainFailedException:
Lock obtain timed out: SimpleFSLock@/home/bwhitman/XXX/XXX/discovered-
solr/data/index/lucene-5b07ebeb7d53a4ddc5a950a458af4acc-write.lock
[11:08:17.150] at org.apache.lucene.store.Lock.obtain(Lock.java:70)
[11:08:17.150] at org.apache.lucene.index.IndexWriter.init
(IndexWriter.java:598)
[11:08:17.150] at org.apache.lucene.index.IndexWriter.<init>
(IndexWriter.java:410)
[11:08:17.150] at org.apache.solr.update.SolrIndexWriter.<init>
(SolrIndexWriter.java:97)
[11:08:17.150] at
org.apache.solr.update.UpdateHandler.createMainIndexWriter
(UpdateHandler.java:121)
[11:08:17.150] at
org.apache.solr.update.DirectUpdateHandler2.openWriter(DirectUpdateHandl
We have the following in our solrconfig re: locks:
<writeLockTimeout>1000</writeLockTimeout>
<commitLockTimeout>10000</commitLockTimeout>
<unlockOnStartup>false</unlockOnStartup>
What can I do to mitigate this problem? Removing the lock file and
restarting resin solves it, but only temporarily.
