Hi Markus, Emir already mentioned tuning *reclaimDeletesWeight which *affects segments about to merge priority. Optimising index time by time, preferably scheduling weekly / fortnight / ..., at low traffic period to never be in such odd position of 80% deleted docs in total index.
Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 On Wed, Oct 4, 2017 at 6:02 PM, Emir Arnautović < emir.arnauto...@sematext.com> wrote: > Hi Markus, > You can set reclaimDeletesWeight in merge settings to some higher value > than default (I think it is 2) to favor segments with deleted docs when > merging. > > HTH, > Emir > -- > Monitoring - Log Management - Alerting - Anomaly Detection > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > > > > On 4 Oct 2017, at 13:31, Markus Jelsma <markus.jel...@openindex.io> > wrote: > > > > Hello, > > > > Using a 6.6.0, i just spotted one of our collections having a core of > which over 80 % of the total number of documents were deleted documents. > > > > It has <mergePolicyFactory > > class="org.apache.solr.index.TieredMergePolicyFactory"/> > configured with no non-default settings. > > > > Is this supposed to happen? How can i prevent these kind of numbers? > > > > Thanks, > > Markus > >