Depending on the query used, deleteByQuery operations can take several minutes
on a very large
index. Currently there is no way to pass an expected duration (a timeout) to
this operation so we're
at the mercy of the system defaults.
When combined with the Apache_Solr_Service_Balancer this can create a problem
since delete
operations that timeout will seem like communication errors - and the class
will resubmit the
operation. Causeing undue stress on the Solr service as it tries to satisfy
them all.
Original issue reported on code.google.com by donovan....@gmail.com on 20 Jul 2009 at 2:13
Original issue reported on code.google.com by
donovan....@gmail.com
on 20 Jul 2009 at 2:13