Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New default merge policy - tiered #998

Closed
kimchy opened this issue Jun 5, 2011 · 0 comments
Closed

New default merge policy - tiered #998

kimchy opened this issue Jun 5, 2011 · 0 comments

Comments

@kimchy
Copy link
Member

kimchy commented Jun 5, 2011

A new merge policy (provided in Lucene 3.2) called tiered which does a better job at merging segments when using near real time.

Provides the following settings:

  • index.merge.policy.expunge_deletes_allowed: When expungeDeletes is called, we only merge away a segment if its delete percentage is over this threshold. Default is 10.
  • index.merge.policy.floor_segment: Segments smaller than this are "rounded up" to this size, ie treated as equal (floor) size for merge selection. This is to prevent frequent flushing of tiny segments from allowing a long tail in the index. Default is 2mb.
  • index.merge.policy.max_merge_at_once: Maximum number of segments to be merged at a time during "normal" merging. Default is 10.
  • index.merge.policy.max_merge_at_once_explicit: Maximum number of segments to be merged at a time, during optimize or expungeDeletes. Default is 30.
  • index.merge.policy.max_merged_segment: Maximum sized segment to produce during normal merging. This setting is approximate: the estimate of the merged segment size is made by summing sizes of to-be-merged segments (compensating for percent deleted docs). Default is 5gb.
  • index.merge.policy.segments_per_tier: Sets the allowed number of segments per tier. Smaller values mean more merging but fewer segments. Default is 10.
  • index.reclaim_deletes_weight: Controls how aggressively merges that reclaim more deletions are favored. Higher values favor selecting merges that reclaim deletions. A value of 0.0 means deletions don't impact merge selection. Defaults to 2.0.
  • index.compound_format: Should the index be stored in compound format or not. Defaults to false.
@kimchy kimchy closed this as completed in 9652ad0 Jun 5, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant