Calling commit after every addition will drastically slow down your indexing throughput, and concurrency (commit is internally synchronized), but should not create lock timeouts, unless you are also opening a new IndexWriter for every addition?
Mike On Thu, Jan 14, 2010 at 12:15 PM, jchang <jchangkihat...@gmail.com> wrote: > > With only 10 concurrent consumers, I do get lock problems. However, I am > calling commit() at the end of each addition. Could I expect better > concurrency without timeouts if I did not commit as often? > > -- > View this message in context: > http://old.nabble.com/Lucene-2.9.0-Near-Real-Time-Indexing-and-lock-timeouts-tp27136743p27164797.html > Sent from the Lucene - Java Developer mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
