honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Tiered merge policy: Change the default max_merge_segment from 5gb to 20gb, closes #1247.

This commit is contained in:
Shay Banon 2011-08-15 21:36:32 +03:00
parent af4b6a1d49
commit da56a4d332
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
modules/elasticsearch/src/main/java/org/elasticsearch/index/merge/policy/TieredMergePolicyProvider.java
View File

@ -68,7 +68,7 @@ public class TieredMergePolicyProvider extends AbstractIndexShardComponent imple
this.maxMergeAtOnce = componentSettings.getAsInt("max_merge_at_once", 10);
this.maxMergeAtOnceExplicit = componentSettings.getAsInt("max_merge_at_once_explicit", 30);
// TODO is this really a good default number for max_merge_segment, what happens for large indices, won't they end up with many segments?
this.maxMergedSegment = componentSettings.getAsBytesSize("max_merge_segment", new ByteSizeValue(5, ByteSizeUnit.GB));
this.maxMergedSegment = componentSettings.getAsBytesSize("max_merge_segment", new ByteSizeValue(20, ByteSizeUnit.GB));
this.segmentsPerTier = componentSettings.getAsDouble("segments_per_tier", 10d);
this.reclaimDeletesWeight = componentSettings.getAsDouble("reclaim_deletes_weight", 2.0d);