: > If you are seeing an increase in "Overlapping onDeckSearchers" when using
: > DocExpirationUpdateProcessorFactory, it's becuase you actaully have docs
: > expiring quite frequently relative to the autoDeletePeriodSeconds and
: > the amount of time needed to warm each of the new searchers.
rm the new
searcher even longer?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Adding-DocExpirationUpdateProcessorFactory-causes-Overlapping-onDeckSearchers-warnings-tp4309155p4309175.html
Sent from the Solr - User mailing list archive at Nabble.com.
: bq: ...is it triggering a commit every 30 seconds, because that's what
: I have the autoDeletePeriodSeconds set to
yes a commit is triggered each time a delete is fired.
: There's a note in the code about making the commits optional, it seems
: fair to raise a JIRA about implementing this.
Okay, I created a JIRA ticket
(https://issues.apache.org/jira/servicedesk/agent/SOLR/issue/SOLR-9841) and
will work on a patch.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Adding-DocExpirationUpdateProcessorFactory-causes-Overlapping-onDeckSearchers-warnings
is
> the case) if the processor simple didn't have to do a commit when it
> expires
> documents, and instead let the auto commit settings handle that.
>
> Do I still need the line:
> name="/update">
> when I have the
> default="true">
> element?
>
instead let the auto commit settings handle that.
>
> Do I still need the line:
> name="/update">
> when I have the
> default="true">
> element?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Adding-DocExpirationUpdateProcessorFactory-causes-Overlapping-onDeckSearchers-warnings-tp4309155.html
> Sent from the Solr - User mailing list archive at Nabble.com.
p://lucene.472066.n3.nabble.com/Adding-DocExpirationUpdateProcessorFactory-causes-Overlapping-onDeckSearchers-warnings-tp4309155.html
Sent from the Solr - User mailing list archive at Nabble.com.
