On 1-Jul-08, at 10:44 PM, Chris Hostetter wrote:
: Yes, updating to a newer version of nightly Solr build could solve
the
: problem, but I am a little afraid to do it since solr-trunk has
switched to
: lucene 2.4-dev.
but did you check wether or not you have maxPendingDeletes
configured as
yonik asked?
That would explain exactly waht you are seeing ... after a certain
number
of deletes have passed, the next one would automaticly force a
commit (and
a newSearcher) and (i believe) subsequent deletes would block until
the
commit is done ... which sounds like exactly what you describe.
It shouldn't cause a commit, just a flushing of deletes. However,
deletes count toward both maxDocs and maxTime for <autocommit>
purposes, so that is the likely explanation.
-Mike
