Did you tried below options
<mergePolicy class="org.apache.lucene.index.TieredMergePolicy">
<double name="forceMergeDeletesPctAllowed">0.0</double>
<double name="reclaimDeletesWeight">10.0</double>
</mergePolicy>
This is from java doc
/** When forceMergeDeletes is called, we only merge away a
* segment if its delete percentage is over this
* threshold. Default is 10%. */
public TieredMergePolicy setForceMergeDeletesPctAllowed(double v) {
if (v < 0.0 || v > 100.0) {
throw new IllegalArgumentException("forceMergeDeletesPctAllowed must
be between 0.0 and 100.0 inclusive (got " + v + ")");
}
forceMergeDeletesPctAllowed = v;
return this;
}
On Fri, Oct 12, 2012 at 3:16 PM, Erick Erickson <erickerick...@gmail.com>wrote:
> Sounds reasonable although I admit I haven't looked deeply.....
>
> Erick
>
> On Fri, Oct 12, 2012 at 3:41 PM, Shawn Heisey <s...@elyograg.org> wrote:
> > On 10/12/2012 6:04 AM, Erick Erickson wrote:
> >>
> >> Hmmm, I dug around in the code and found this bit:
> >> * Forces merging of all segments that have deleted
> >> * documents. The actual merges to be executed are
> >> * determined by the {@link MergePolicy}. For example,
> >> * the default {@link TieredMergePolicy} will only
> >> * pick a segment if the percentage of
> >> * deleted docs is over 10%.
> >>
> >> see IndexWriter.forceMergeDeletes. So perhaps this limit
> >> was never hit?
> >
> >
> > My own digging based on yours turned up this:
> >
> > https://issues.apache.org/jira/browse/SOLR-2725
> >
> > This sounds like there is currently no way to change this in the Solr
> > config, so it looks like my choices right now are to make a source code
> > change and respin the Solr 3.5.0 that I'm using or just continue to use
> > optimize with no options until SOLR-2725 gets resolved and I can upgrade.
> > Is that right?
> >
> > Thanks,
> > Shawn
> >
>
