: 02-Nov-2009 10:35:27 org.apache.solr.update.SolrIndexWriter finalize : SEVERE: SolrIndexWriter was not closed prior to finalize(), indicates : a bug -- POSSIBLE RESOURCE LEAK!!!
can you post some context showing what the logs look like just before these errors? I'm not sure what might be causing lock collision but your guess about commit's taking too long and overlapping is a good one -- what do the log messages about the commits say arround the time these errors start? the commit logs when it finishes and how long it takes so it's easy to spot. increasing your writeLockTimeout is probably a good idea, but i'm still confused as to why the whole server would lock up until you delete the index and restart, at worst i would expect the update/commit attempts that time out getting the lock to complain loudly, but then the "slow" one would eventually finish and subsequent attempts would work ok. ...very odd. -Hoss
