It is possible that a previous operation on the index left the lock open.Actually this is exactly the problem... I ran some single index tests and a single process seems to read from it.
Leaving the IndexWriter or Reader open without closing them ( in a finally
block ) could cause this.
The problem is that we were running under Tomcat with diff webapps for testing and didn't run into this problem before. We had an 11G index that just took a while to open and during this open Lucene was creating a lock.
I wasn't sure that Tomcat was multithreading this so maybe it is and it's just taking longer to open the lock in some situations.
Kevin
--
Please reply using PGP.
http://peerfear.org/pubkey.asc NewsMonster - http://www.newsmonster.org/
Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster
signature.asc
Description: OpenPGP digital signature
