Also noticed that "waitSearcher" parameter value is not honored inside commit. It is always defaulted to true which makes it slow during indexing.
What we are trying to do is use an invalid query (which wont return any results) as a warming query. This way the commit returns faster. Are we doing something wrong here? Thanks, Tirthankar -----Original Message----- From: Jonathan Rochkind [mailto:rochk...@jhu.edu] Sent: Monday, July 18, 2011 11:38 AM To: solr-user@lucene.apache.org; yo...@lucidimagination.com Subject: Re: NRT and commit behavior In practice, in my experience at least, a very 'expensive' commit can still slow down searches significantly, I think just due to CPU (or i/o?) starvation. Not sure anything can be done about that. That's my experience in Solr 1.4.1, but since searches have always been async with commits, it probably is the same situation even in more recent versions, I'd guess. On 7/18/2011 11:07 AM, Yonik Seeley wrote: > On Mon, Jul 18, 2011 at 10:53 AM, Nicholas Chase<nch...@earthlink.net> wrote: >> Very glad to hear that NRT is finally here! But my question is this: >> will things still come to a standstill during a commit? > New updates can now proceed in parallel with a commit, and searches > have always been completely asynchronous w.r.t. commits. > > -Yonik > http://www.lucidimagination.com > ******************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you." *********************************************************
