From da56a4d33291ea4fefecb2ec47e435b40f1e5501 Mon Sep 17 00:00:00 2001 From: Shay Banon Date: Mon, 15 Aug 2011 21:36:32 +0300 Subject: [PATCH] Tiered merge policy: Change the default max_merge_segment from 5gb to 20gb, closes #1247. --- .../index/merge/policy/TieredMergePolicyProvider.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/elasticsearch/src/main/java/org/elasticsearch/index/merge/policy/TieredMergePolicyProvider.java b/modules/elasticsearch/src/main/java/org/elasticsearch/index/merge/policy/TieredMergePolicyProvider.java index 72a10b0e1ea..6b78f1430bd 100644 --- a/modules/elasticsearch/src/main/java/org/elasticsearch/index/merge/policy/TieredMergePolicyProvider.java +++ b/modules/elasticsearch/src/main/java/org/elasticsearch/index/merge/policy/TieredMergePolicyProvider.java @@ -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);