How to set max_merged_segment at startup?

Elastic Stack Elasticsearch
3

Here is the issue:
Tiered merge policy setting: `max_merge_segment` misnamed and should be `max_merged_segment` · Issue #1280 · elastic/elasticsearch · GitHub.

On Fri, Aug 26, 2011 at 5:14 PM, Shay Banon kimchy@gmail.com wrote:

When you set it in the configuration file, then it will be applied if that
node is the master, and the index gets created. You can also specify the
same setting when you create the index as an index setting.

I see where the problem is..., in the configuration level on startup, the
setting is misnamed, can called: max_merge_segment (merge instead of
merged), I will fix that.

On Thu, Aug 25, 2011 at 3:01 AM, Tom Le dottom@gmail.com wrote:

Is there a way to set max_merged_segment (or any of the merge
settings) at startup?

I can set max_merged_segment dynamically like this and it works as
expected:

curl -XPUT localhost:9200/myindex/_settings -d '{
"index" : {
"merge.policy.max_merged_segment" : "2g"
}
}'

What I would like to do is set these for all indexes by default at
startup, but this does not set it:

index:
number_of_shards: 1
number_of_replicas: 0
merge.policy.max_merged_segment: 2g

This does not work either:

index:
number_of_shards: 1
number_of_replicas: 0

 merge:
   policy:
     max_merged_segment: 2g

I have also tried substituting "max_merge_size" for
"max_merged_segment".