Your response contradicts the wiki's description of mergeFactor: http://wiki.apache.org/solr/SolrPerformanceFactors#mergeFactor -- which clearly states that the indexes are merged into a single segment. It makes no reference to "optimize" to trigger this condition. If what you say is true, and we agree that the mergeFactor is the upper bound of the number of segments, then what is the lower bound of the number of segments seen for an index that has not been optimized? Always 2, or some function of mergeFactor?
~ David Smiley Jay Hill wrote: > > With a mergeFactor set to anything > 1 you would never have only one > segment > - unless you optimized. So Lucene will never naturally merge all the > segments into one. Unless, I suppose, the mergeFactor was set to 1, but > I've > never tested that. It's hard to picture how that would work. > > If I understand correctly, the same actions occur (deleted documents are > removed, etc.) because an optimize is only a multiway merge down to one > segment, whereas normal merging is triggered by the mergeFactor, but does > not have a "target" segment count to merge down to. > > -Jay > ... > -- View this message in context: http://old.nabble.com/optimize-is-taking-too-much-time-tp27561570p27693177.html Sent from the Solr - User mailing list archive at Nabble.com.
