Hi All, We are seeing an issue with solr where solr is failing to initialize the cores with the following errors. We have gone through the solr documentation on these errors and its mentioned that this could happen when solr is running in clustered mode. But in our case solr is deployed in 2N-active deployment model. Also all the other configurations are done as recommended by solr.
WARN - 2016-02-26 05:49:29.050; org.apache.solr.schema.IndexSchema; no uniqueKey specified in schema. WARN - 2016-02-26 05:49:29.075; org.apache.solr.schema.IndexSchema; no uniqueKey specified in schema. WARN - 2016-02-26 05:49:29.191; org.apache.solr.core.SolrCore; [cm_history] WARNING: Solr index directory '/foo/solr/cm_history/data/index/' is locked. Unlocking... WARN - 2016-02-26 05:49:29.680; org.apache.solr.rest.ManagedResource; No stored data found for /rest/managed Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@/foo/solr/data/index/write.lock<mailto:SimpleFSLock@/foo/solr/data/index/write.lock> at org.apache.lucene.store.Lock.obtain(Lock.java:89) at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:710) at org.apache.solr.update.SolrIndexWriter.<init>(SolrIndexWriter.java:77) at org.apache.solr.update.SolrIndexWriter.create(SolrIndexWriter.java:64) ERROR - 2016-02-26 07:15:01.412; org.apache.solr.update.SolrIndexWriter; SolrIndexWriter was not closed prior to finalize(), indicates a bug -- POSSIBLE RESOURCE LEAK!!! ERROR - 2016-02-26 07:15:01.413; org.apache.solr.update.SolrIndexWriter; Error closing IndexWriter, trying rollback java.lang.NullPointerException at org.apache.lucene.index.IndexWriter.closeInternal(IndexWriter.java:985) at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:935) at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:897) at org.apache.solr.update.SolrIndexWriter.close(SolrIndexWriter.java:132) Here is the scenario: 1. We are using solr 4.8.1 2. This installation runs 3 different cores in it. All cores use <lockType>${solr.lock.type:simple}</lockType>. 3. We are seeing above issue while solr starts coming up for the first time. Any pointers what could be corrected here. Regards, Prateek Jain
