Thanks for the response Hoss. Sorry for replying late was on a business trip. The server was indexing as well as searching at the same time and it was configured for a Native file lock, could that be the issue ? I got another server so moved it to a Master & slave configuration with file lock being single on both machines, that solved the issue.
I would however love to know what caused that error (its never too late to learn, right ???) Thanks, Ravi Kiran On Mon, Feb 7, 2011 at 2:51 PM, Chris Hostetter <hossman_luc...@fucit.org>wrote: > > : While reloading a core I got this following error, when does > this > : occur ? Prior to this exception I do not see anything wrong in the logs. > > well, there are realy two distinct types of "errors" in your log... > > : > [#|2011-02-01T13:02:36.697-0500|SEVERE|sun-appserver2.1|org.apache.solr.servlet.SolrDispatchFilter|_ThreadID=25;_ThreadName=httpWorkerThread-9001-5;_RequestID=450f6337-1f5c-42bc-a572-f0924de36b56;|org.apache.lucene.store.LockObtainFailedException: > : Lock obtain timed out: NativeFSLock@ > : > /data/solr/core/solr-data/index/lucene-7dc773a074342fa21d7d5ba09fc80678-write.lock > : at org.apache.lucene.store.Lock.obtain(Lock.java:85) > : at > org.apache.lucene.index.IndexWriter.init(IndexWriter.java:1565) > : at > org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1421) > > ...this is error #1, indicating that for some reason the IndexWriter Solr > wasn't trying to create wasn't able to get a Native Filesystem lock on > your index directory -- is it possible you have two intsances of Solr (or > two solr cores) trying to re-use the same data directory? > > (diagnosing exampley why you got this error also requires knowing what > Filesystem you are using). > > : > [#|2011-02-01T13:02:40.330-0500|SEVERE|sun-appserver2.1|org.apache.solr.update.SolrIndexWriter|_ThreadID=82;_ThreadName=Finalizer;_RequestID=121fac59-7b08-46b9-acaa-5c5462418dc7;|SolrIndexWriter > : was not closed prior to finalize(), indicates a bug -- POSSIBLE RESOURCE > : LEAK!!!|#] > : > : > [#|2011-02-01T13:02:40.330-0500|SEVERE|sun-appserver2.1|org.apache.solr.update.SolrIndexWriter|_ThreadID=82;_ThreadName=Finalizer;_RequestID=121fac59-7b08-46b9-acaa-5c5462418dc7;|SolrIndexWriter > : was not closed prior to finalize(), indicates a bug -- POSSIBLE RESOURCE > : LEAK!!!|#] > > ...these errors are warning you that something very unexpected was > discovered when the the Garbage Collector tried to cleanup the > SolrIndexWriter -- it found that the SolrIndexWriter had never been > formally closed. > > In normal operation, this might indicate the existence of a bug in code > not managing it's resources properly --and in fact, it does indicate the > existence of a bug in that evidently a Lock timed out failure doesn't > cause the SOlrIndexWriter to be closed -- but in your case it's not really > something to be worried about -- it's just a cascading effect of the first > error. > > -Hoss >
