> Yes, coordination between the main index searcher, the index writer, > and the index reader needed to delete other documents.
Can you point me to any documentation/code that describes this implementation? > That's weird... I've never seen that. > The lucene write lock is only obtained when the IndexWriter is created. > Can you post the relevant part of the log file where the exception > happens? After doing some more testing, I believe it was a stale lock file that was causing me to have these lock issues yesterday - sorry for the false alarm :) > Also, unless you have at least 6 CPU cores or so, you are unlikely to > see greater throughput with 10 threads. If you add multiple documents > per HTTP-POST (such that HTTP latency is minimized), the best setting > would probably be nThreads == nCores. For a single doc per POST, more > threads will serve to cover the latency and keep Solr busy. I agree with your thinking here. My requirement for a large number of threads is somewhat of an artifact of my current system design. I'm trying not to serialize the system's processing at the point of indexing. -- View this message in context: http://www.nabble.com/Index-Concurrency-tf3718634.html#a10424207 Sent from the Solr - User mailing list archive at Nabble.com.
