I was going to say... that exception should never happen since solr controls and synchronizes adds/deletes at a higher layer (with only one solr instance accessing an index, we don't really need lucene level locking at all).
One major cause of this is a crash/restart of the JVM leaving a stale lock file behind. Those can be removed automatically at startup with a tweak in solrconfig.xml -Yonik On 7/12/07, Matthew Runo <[EMAIL PROTECTED]> wrote:
It looks like somehow the write.lock got hung. I manually removed the lock, and now things are good. Very strange.
