lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <>
Subject Re: Example setting TieredMergePolicy for Solr 3.3 or 3.4?
Date Wed, 21 Sep 2011 17:18:20 GMT
On 9/20/2011 4:09 PM, Robert Muir wrote:
> yes, mergeFactory=10 is interpreted as both segmentsPerTier and 
> maxMergeAtOnce. yes, specifying explicit TieredMP parameters will 
> override whatever you set in mergeFactor (which is basically only 
> interpreted to be backwards compatible) this is why i created this 
> confusing test configuration: to test this exact case. 

I've got a checked out lucene_solr_3_4 and this isn't what I'm seeing.
Solr Implementation Version: 3.4-SNAPSHOT 1173320M - root - 2011-09-21 

With no mergeFactor defined, maxMergeAtOnce and segmentsPerTier seem to 
be ignored.  I've got both set to 35, but Solr is merging every 10 
segments.  I haven't tried explicitly setting mergeFactor yet to see if 
that will make the other settings override it, I'm letting the current 
import finish first.

Here's the relevant config pieces.  These two sections are in separate 
files incorporated into solrconfig.xml using xinclude:

<mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler">
<int name="maxMergeCount">4</int>
<int name="maxThreadCount">4</int>

<mergePolicy class="org.apache.lucene.index.TieredMergePolicy">
<int name="maxMergeAtOnce">35</int>
<int name="segmentsPerTier">35</int>
<int name="maxMergeAtOnceExplicit">105</int>


View raw message