Merge Policies in Solr

 

I happened to get an chance to optimize the Solr configuration of Home Depot Canada. My mainly improvement is focused on the segments merge policies. However there are limited resources on-line, I spent some time looking into the source code of LogMergePolicy and TieredMergePolicy. I am going to share how does these two mostly used Solr merge polices work and my findings.

In these two algorithms, both would not merge segment which is being merged (By default, using ConcurrentMergeScheduler, Solr executes each merge in a separate thread).

Log Merge Policy

Assumptions:

The number of merge-able segments is N; Level log span is P=0.75(by default); The merge factor is M; Size of a segment (exclude deflection documents) in MB is , if , then ; Any segment whose size is greater than 2 GiB will never be merged (By default, maxMergeSize has a fixed value of 2 GiB.).

Algorithm:

  1. Sort all merge-able segments by name (created timestamp);
  2. Calculate level info value for each segment:

  3. Set the pointer to the first segment (). Calculate current level boundary:

    Maximum level info value:

    Minimum level info value:

  4. Find the newest segment() whose level info value is greater than . All segments older than or equal to this segment belong to the current level. If the number of segments of the current level is bigger than M, merge M segments recursively until current level’s size is smaller than M.

  5. Set the pointer and go to step 3, until ;

Tiered Merge Policy

Assumptions:

The number of merge-able segment is N; Size in MB (exclude deletion documents) of a segment is , if , then ; Size in MB(include deletion documents) is ; Maximum merge at once is M; Segments per tier is T; Any segment whose size is greater than 2.5 GiB will be excluded(By dufault, maxMergedSegmentBytes = ).

Algorithm:

  1. Sort all merge-able segments by size desc.

  2. It assumes, for tier k, the average size of a segment is :

    So, the minimum Tier needed to hold all documents:

    Then, the maximum segments needed (its our maximum budget):

  3. If find best merge combination based on Merge Score Sc:

    Merge score of segments combination (i to i+M) is calculated by skew (basically how “equally sized” the segments being merged are), total size (smaller merges are favored but if total size > 5 GB, skew will be set to ), and how many deleted documents will be reclaimed as below:

  4. Merge segments combination from i to i+M with smallest merge score .

Conclusion:

TeiredMerge Algorithm tries to find the best merge combinations based on several factors(segment sizes, balance, deletion rate). However, LogMerge Algorithm merges segments based on created time stamp only. The sizes of merged segments in LogMerge are unpredictable. Solr started to use TeiredMerge algorithm as the default algorithm after it introduced. Based on Michael McCandless, the author of “Lucene in Action”: To minimize merge cost, we ideally would merge only equal-sized segments, and merge a larger number of segments at a time. When I tried to solve the real problem, I tried to produce equal-sized segments by using “Auto Commit” and I set maxMergeAtOnce to a bigger number to make sure more documents are merged at a time. Moreover, I controlled allowed segments amount(maximum budget) to a smaller number by setting segmentPerTeir to a lower value.

References:

  1. Visualizing Lucene’s segment merges

  2. Solr: Optimize Is Not Bad For You Deep Dive Into The Segment Merge Abyss