lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hostetter <hossman_luc...@fucit.org>
Subject Re: SolrIndexWriter was not closed prior to finalize(), indicates a bug -- POSSIBLE RESOURCE LEAK!!!
Date Mon, 07 Feb 2011 19:51:36 GMT

:           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

Mime
View raw message