On 11/6/2015 2:23 PM, Pushkar Raste wrote: > I may be wrong but I think 'delete' and 'optimize' can not be executed > concurrently on a Lucene index
It certainly is looking that way. After discussing it with Hoss on IRC, I tried a manual test where I started an optimize and then did some "add" requests from the admin UI. Those succeeded, but whenever my SolrJ code does a delete request on an index that is being optimized, that request blocks until either the optimize finishes or the SO_TIMEOUT (15 minutes) that I configured on HttpClient is reached. My SolrJ code always starts with any deletes that need to happen, then moves onto other changes like reinserts and adds. If delete and optimize cannot happen at the same time, is that a bug? This is happening on both 4.9.1 and 5.2.1. Thanks, Shawn
