[ http://issues.apache.org/jira/browse/LUCENE-307?page=comments#action_12446688 ] Michael McCandless commented on LUCENE-307: -------------------------------------------
I think we can close this one? We now have locking implementation (*LockFactory) decoupled from directory implementation, so you can do in-JVM locking with an FSDirectory. We also have a native locking LockFactory implementation (LUCENE-678 ). I'm still surprised that native locking alone would prevent the starvation issue. If you try to open/close readers & writers too frequently against a single index there will inevitably be starvation. Lockless commits (LUCENE-701 ) can help somewhat in that you should not see IOExceptions anymore, but, it will still hit starvation by doing many retries before opening an index. In any event, I think these open rates are far beyond where Lucene would normally be used so I don't think we should spend time fixing starvation. > Lock obtain time out errors when opening readers and writers > ------------------------------------------------------------ > > Key: LUCENE-307 > URL: http://issues.apache.org/jira/browse/LUCENE-307 > Project: Lucene - Java > Issue Type: Bug > Components: Other > Affects Versions: 1.4 > Environment: Operating System: All > Platform: All > Reporter: Reece (YT) > Assigned To: Lucene Developers > Attachments: FSLock.java, TestLuceneLocks.java > > > The attached Java file shows a locking issue that occurs with Lucene 1.4.2. > One thread opens and closes an IndexReader. The other thread opens an > IndexWriter, adds a document and then closes the IndexWriter. I would expect > that this app should be able to happily run without an issues. > It fails with: > java.io.IOException: Lock obtain timed out > Is this expected? I thought a Reader could be opened while a Writer is > adding a > document. > I am able to get the error in less than 5 minutes when running this on Windows > XP and Mac OS X. > Any help is appreciated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
