You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Dragisa Krsmanovic <dk...@plos.org> on 2010/06/09 00:36:13 UTC
Optimize with waitFlush="false" and waitSearcher="false" takes a long time
When we send <optimize waitFlush="false" waitSearcher="false"/> the HTTP
response sometimes takes more than 60s and our client times out after
that. Whole operation takes 200+ seconds. Isn't waitFlush="false" and
waitSearcher="false" supposed to tell Solr to return response
immediately ?
INFO: start
commit(optimize=true,waitFlush=false,waitSearcher=false,expungeDeletes=false)
Jun 7, 2010 9:04:25 PM org.apache.solr.core.SolrCore execute
INFO: [] webapp=/solr path=/update params={} status=0 QTime=217900
--
Dragisa Krsmanovic
Java Developer
Public Library of Science
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This email is confidential to the intended recipient. If you have received it in error, please notify the sender and delete it from your
system. Any unauthorized use, disclosure or copying is not permitted. The views or opinions presented are solely those of the sender and do
not necessarily represent those of Public Library of Science unless otherwise specifically stated. Please note that neither Public Library
of Science nor any of its agents accept any responsibility for any viruses that may be contained in this e-mail or its attachments and it
is your responsibility to scan the e-mail and attachments (if any).
Re: Optimize with waitFlush="false" and waitSearcher="false" takes
a long time
Posted by Chris Hostetter <ho...@fucit.org>.
: Because waitFlush doesn't work currently, your client
i didn't realize waitFlush is currently ignored ... is that an open bug
in Jira, or was it a neccessary change because of something else? do we
at least log an warning if someone tries to use waitFlush=false?
-Hoss
Re: Optimize with waitFlush="false" and waitSearcher="false" takes
a long time
Posted by Koji Sekiguchi <ko...@r.email.ne.jp>.
(10/06/09 7:36), Dragisa Krsmanovic wrote:
> When we send<optimize waitFlush="false" waitSearcher="false"/> the HTTP
> response sometimes takes more than 60s and our client times out after
> that. Whole operation takes 200+ seconds. Isn't waitFlush="false" and
> waitSearcher="false" supposed to tell Solr to return response
> immediately ?
>
> INFO: start
> commit(optimize=true,waitFlush=false,waitSearcher=false,expungeDeletes=false)
> Jun 7, 2010 9:04:25 PM org.apache.solr.core.SolrCore execute
> INFO: [] webapp=/solr path=/update params={} status=0 QTime=217900
>
Because waitFlush doesn't work currently, your client
waits until optimize done. (Then waitSearcher=false does
work correctly as it is specified, you got the response
immediately after optimize done.)
Koji
--
http://www.rondhuit.com/en/
Re: Optimize with waitFlush="false" and waitSearcher="false" takes
a long time
Posted by Mark Miller <ma...@gmail.com>.
On 6/8/10 3:36 PM, Dragisa Krsmanovic wrote:
> When we send<optimize waitFlush="false" waitSearcher="false"/> the HTTP
> response sometimes takes more than 60s and our client times out after
> that. Whole operation takes 200+ seconds. Isn't waitFlush="false" and
> waitSearcher="false" supposed to tell Solr to return response
> immediately ?
>
> INFO: start
> commit(optimize=true,waitFlush=false,waitSearcher=false,expungeDeletes=false)
> Jun 7, 2010 9:04:25 PM org.apache.solr.core.SolrCore execute
> INFO: [] webapp=/solr path=/update params={} status=0 QTime=217900
>
>
We read waitFlush all over and set it - but I don't think current code
respects it.
Also, that command will wait for the optimize anyway.
--
- Mark
http://www.lucidimagination.com