(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/

Reply via email to