I believe that when you commit, a new IndexReader is created, which is warmed, etc. New incoming queries will be sent to this new IndexReader. Once all previously existing queries have been answered, the old IndexReader will shut down.
The commit doesn't wait for the query to finish, but it shouldn't impact the results of that query either. What may be impacted is overall system performance while you have 2 IndexReaders in play. There will always be some amount of overlap, but it may be drawn out by the long query. -Todd Feak -----Original Message----- From: wojtekpia [mailto:wojte...@hotmail.com] Sent: Tuesday, January 13, 2009 2:18 PM To: solr-user@lucene.apache.org Subject: Commiting index while time-consuming query is running Once in a while my Solr instance receives a query that takes a really long time to execute (several minutes or more). What will happen if I update my index (and commit) while one of these really long queries is executing? Will Solr wait for the query to complete before it commits my update? (on a side note, I'm re-working my UI to eliminate these queries) Thanks! -- View this message in context: http://www.nabble.com/Commiting-index-while-time-consuming-query-is-runn ing-tp21445704p21445704.html Sent from the Solr - User mailing list archive at Nabble.com.