Hello, I am using Lucene 2.4.0 and am getting org.apache.lucene.store.LockObtainFailedException's when I have a backed up queue of items to index (with multiple concurrent writers). Of course, if I throttle all my writer threads to 1, I don't get the exception, but I'm hoping to write faster than that. Also, when I have multiple index writer threads, it's not that much faster anyhow, I assume because the bottle neck is on one the index file.
Will 2.9.0 help? I've read about the near real time indexing. Will this allow me to have: 1) Multiple threads indexing items all at the same time, achieving appreciably faster throughput than only one thread? 2) And avoid getting org.apache.lucene.store.LockObtainFailedException's? 3) Have this all near real time? And generally, if anybody has any advice on high-throughput indexing with Lucene and what kind of numbers I can acheive, I'd welcome the feedback. Thanks, John -- View this message in context: http://old.nabble.com/Lucene-2.9.0-Near-Real-Time-Indexing-and-lock-timeouts-tp27136743p27136743.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
