Thanks Shawn for your reply. Actually, initially I only used <mergeFactor>3</mergeFactor> in config without defining any policy. But was not able to find any positive results of merging as Number of FDT and FDX was still the same as before. Yesterday, tried these default setting from Solr documentation mentioned earlier but in vain. So, Should i use mergeFactor with LogMergePolicy? What is your recommendation for getting desired results.
Thank you. Waiting for your response. Best Regards, *Usman Parvez* | Principal Software Engineer | NorthBay Solutions *Skype*: usman.parvez | *Cell*: +92 322 4277077 | +92 301 8466124 On Wed, Mar 26, 2014 at 9:41 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 3/26/2014 8:23 AM, Usman Parvez wrote: > >> Hi Team, >> >> I'm setting up merge factor for my Solr index. Defined following config >> values in solrConfig.xml. >> >> <mergePolicy class="org.apache.lucene.index.TieredMergePolicy"> >> >>> <int name="maxMergeAtOnce">10</int> >>> <int name="segmentsPerTier">10</int> >>> </mergePolicy> >>> <mergeFactor>3</mergeFactor> >>> <mergeScheduler class="org.apache.lucene.index. >>> ConcurrentMergeScheduler"/> >>> >> >> Number of FDT, FDX and Doc files in index folder is still 22 each. Am I >> missing something? >> I just want to enable auto merge with mergeFactor value 3 to avoid >> optimization, due to large index it take hours for optimization and >> replication. >> > > With TieredMergePolicy, mergeFactor is not actually valid config. Solr > does accept it, but it just changes the settings for maxMergeAtOnce and > segmentsPerTier. I don't know whether it changes maxMergeAtOnceExplicit, > which defaults to 30. > > Because you have explicitly defined maxMergeAtOnce and segmentsPerTier, > your mergeFactor setting is completely ignored. Change those values > directly instead. > > This is going to result in a lot of merging. It may not be any better > than optimizing, and over time, might actually be worse. > > Thanks, > Shawn > >
