The default is 2.0, and higher values will more strongly favor merging
segments with deletes.
I think 20.0 is likely way too high ... maybe try 3-5?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Jun 18, 2013 at 6:46 PM, Petersen, Robert
robert.peter...@mail.rakuten.com wrote:
Hi
Subject: Re: TieredMergePolicy reclaimDeletesWeight
The default is 2.0, and higher values will more strongly favor merging segments
with deletes.
I think 20.0 is likely way too high ... maybe try 3-5?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Jun 18, 2013 at 6:46 PM, Petersen, Robert
...@mikemccandless.com]
Sent: Wednesday, June 19, 2013 9:33 AM
To: solr-user@lucene.apache.org
Subject: Re: TieredMergePolicy reclaimDeletesWeight
The default is 2.0, and higher values will more strongly favor merging
segments with deletes.
I think 20.0 is likely way too high ... maybe try 3-5?
Mike
Oh! Thanks for the info. I'll change that right away.
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Wednesday, June 19, 2013 10:42 AM
To: solr-user@lucene.apache.org
Subject: Re: TieredMergePolicy reclaimDeletesWeight
Way too high would cause
Hi
In continuing a previous conversation, I am attempting to not have to do
optimizes on our continuously updated index in solr3.6.1 and I came across the
mention of the reclaimDeletesWeight setting in this blog:
http://blog.mikemccandless.com/2011/02/visualizing-lucenes-segment-merges.html
