: 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
NOTE: that message is logged on startup when an old lock file is found ... it's not the cause of your server "going down" ... it's a symptom of an earlier problem. Think of hte lock file like a PID file ... by default, Solr doesn't want to startup if there's a record of another instance running -- that instance may no longer be running, but Solr has to assume it is because hte lock file is there. Using unLockonStartup, or switching lockType to "single" will ensure that if solr crashes it can start back up without tripping over the old lock file -- but it still doesn't tell you why you had a crash in the first place. -Hoss
