# Mysterious index settings overwriting cluster settings
**URL:** https://discuss.elastic.co/t/mysterious-index-settings-overwriting-cluster-settings/21622
**Category:** Elasticsearch
**Created:** [January 14, 2015, 12:52am UTC](https://discuss.elastic.co/t/mysterious-index-settings-overwriting-cluster-settings/21622 "2015-01-14T00:52:45Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Chris\_Neal](https://discuss.elastic.co/u/Chris_Neal)
#### Post date: [January 14, 2015, 12:52am UTC](https://discuss.elastic.co/t/mysterious-index-settings-overwriting-cluster-settings/21622/1 "2015-01-14T00:52:45Z")
Hi all.
I'm reposting an earlier thread of mine with a more appropriate subject in
hopes that someone might have an idea on this one. 馃檪
Each node in my cluster has its configuration set via elasticsearch.yml
only. I do not apply any index level settings, however the nodes in the
cluster are overwriting my config settings with the defaults. I have been
unable to figure out why this is happening, and was hoping someone else
might.
My elasticsearch.yml file defines these settings:
index:
codec:
bloom:
load: false
merge:
policy:
max\_merge\_at\_once: 4
max\_merge\_at\_once\_explicit: 4
max\_merged\_segment: 1gb
segments\_per\_tier: 4
type: tiered
scheduler:
max\_thread\_count: 1
type: concurrent
number\_of\_replicas: 0
number\_of\_shards: 1
refresh\_interval: 5s
From the head plugin, I can see these settings are in effect:
- settings: {
- index: {
- codec: {
- bloom: {
- load: false
}
}
- number\_of\_replicas: 1
- number\_of\_shards: 6
- translog: {
- flush\_threshold\_size: 1GB
}
- search: {
- slowlog: {
- threshold: {
- fetch: {
- warn: 2s
- info: 1s
}
- index: {
- warn: 10s
- info: 5s
}
- query: {
- warn: 10s
- info: 5s
}
}
}
}
- refresh\_interval: 60s
- merge: {
- scheduler: {
- type: concurrent
- max\_thread\_count: 1
}
- policy: {
- type: tiered
- max\_merged\_segment: 1gb
- max\_merge\_at\_once\_explicit: 4
- max\_merge\_at\_once: 4
- segments\_per\_tier: 4
}
}
}
- bootstrap: {
- mlockall: true
}
-
But each node outputs this on new index creation:
[2015-01-13 02:12:52,062][INFO][index.merge.policy]
[elasticsearch-test] [test-20150113][1] updating [segments\_per\_tier] from
[4.0] to [10.0]
[2015-01-13 02:12:52,062][INFO][index.merge.policy]
[elasticsearch-test] [test-20150113][1] updating [max\_merge\_at\_once] from
[4] to [10]
[2015-01-13 02:12:52,062][INFO][index.merge.policy]
[elasticsearch-test] [test-20150113][1] updating
[max\_merge\_at\_once\_explicit] from [4] to [30]
[2015-01-13 02:12:52,062][INFO][index.merge.policy]
[elasticsearch-test] [test-20150113][1] updating [max\_merged\_segment] from
[1024.0mb] to [5gb]
This is happening both on two clusters for me. My "regular" ES cluster of
3 nodes, and my dedicated Marvel cluster of 1 node. So strange.
[2015-01-06 04:04:53,320][INFO][cluster.metadata]
[elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06] update\_mapping
[cluster\_state] (dynamic)
[2015-01-06 04:04:56,704][INFO][index.merge.policy]
[elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
[segments\_per\_tier] from [4.0] to [10.0]
[2015-01-06 04:04:56,704][INFO][index.merge.policy]
[elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
[max\_merge\_at\_once] from [4] to [10]
[2015-01-06 04:04:56,704][INFO][index.merge.policy]
[elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
[max\_merge\_at\_once\_explicit] from [4] to [30]
[2015-01-06 04:04:56,704][INFO][index.merge.policy]
[elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
[max\_merged\_segment] from [1024.0mb] to [5gb]
I am really stumped on why this is happening!
Thanks so much for your time.
Chris
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@masaru](https://discuss.elastic.co/u/masaru)
#### Post date: [January 14, 2015, 2:42am UTC](https://discuss.elastic.co/t/mysterious-index-settings-overwriting-cluster-settings/21622/2 "2015-01-14T02:42:21Z")
Hi Chris,
I think you hit this issue
[Merge policy settings are ignored when set in YML 路 Issue #8890 路 elastic/elasticsearch 路 GitHub](https://github.com/elasticsearch/elasticsearch/issues/8890).
Workaround would be to use index template (as described in the issue) or to
update them by indices settings API.
Masaru
On Wed, Jan 14, 2015 at 9:52 AM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net)
wrote:
> Hi all.
>
> I'm reposting an earlier thread of mine with a more appropriate subject in
> hopes that someone might have an idea on this one. 馃檪
>
> Each node in my cluster has its configuration set via elasticsearch.yml
> only. I do not apply any index level settings, however the nodes in the
> cluster are overwriting my config settings with the defaults. I have been
> unable to figure out why this is happening, and was hoping someone else
> might.
>
> My elasticsearch.yml file defines these settings:
>
> index:
> codec:
> bloom:
> load: false
> merge:
> policy:
> max\_merge\_at\_once: 4
> max\_merge\_at\_once\_explicit: 4
> max\_merged\_segment: 1gb
> segments\_per\_tier: 4
> type: tiered
> scheduler:
> max\_thread\_count: 1
> type: concurrent
> number\_of\_replicas: 0
> number\_of\_shards: 1
> refresh\_interval: 5s
>
> From the head plugin, I can see these settings are in effect:
>
> - settings: {
> - index: {
> - codec: {
> - bloom: {
> - load: false
> }
> }
> - number\_of\_replicas: 1
> - number\_of\_shards: 6
> - translog: {
> - flush\_threshold\_size: 1GB
> }
> - search: {
> - slowlog: {
> - threshold: {
> - fetch: {
> - warn: 2s
> - info: 1s
> }
> - index: {
> - warn: 10s
> - info: 5s
> }
> - query: {
> - warn: 10s
> - info: 5s
> }
> }
> }
> }
> - refresh\_interval: 60s
> - merge: {
> - scheduler: {
> - type: concurrent
> - max\_thread\_count: 1
> }
> - policy: {
> - type: tiered
> - max\_merged\_segment: 1gb
> - max\_merge\_at\_once\_explicit: 4
> - max\_merge\_at\_once: 4
> - segments\_per\_tier: 4
> }
> }
> }
> - bootstrap: {
> - mlockall: true
> }
> -
>
> But each node outputs this on new index creation:
>
> [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> [elasticsearch-test] [test-20150113][1] updating [segments\_per\_tier] from
> [4.0] to [10.0]
> [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> [elasticsearch-test] [test-20150113][1] updating [max\_merge\_at\_once] from
> [4] to [10]
> [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> [elasticsearch-test] [test-20150113][1] updating
> [max\_merge\_at\_once\_explicit] from [4] to [30]
> [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> [elasticsearch-test] [test-20150113][1] updating [max\_merged\_segment] from
> [1024.0mb] to [5gb]
>
> This is happening both on two clusters for me. My "regular" ES cluster of
> 3 nodes, and my dedicated Marvel cluster of 1 node. So strange.
>
> [2015-01-06 04:04:53,320][INFO][cluster.metadata]
> [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06] update\_mapping
> [cluster\_state] (dynamic)
> [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> [segments\_per\_tier] from [4.0] to [10.0]
> [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> [max\_merge\_at\_once] from [4] to [10]
> [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> [max\_merge\_at\_once\_explicit] from [4] to [30]
> [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> [max\_merged\_segment] from [1024.0mb] to [5gb]
>
> I am really stumped on why this is happening!
> Thanks so much for your time.
> Chris
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com)
> [https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com?utm_medium=email&utm_source=footer)
> .
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug\_ETVoFwpY\_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug_ETVoFwpY_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Chris\_Neal](https://discuss.elastic.co/u/Chris_Neal)
#### Post date: [January 14, 2015, 3:07am UTC](https://discuss.elastic.co/t/mysterious-index-settings-overwriting-cluster-settings/21622/3 "2015-01-14T03:07:14Z")
Hi Masaru,
Beautiful! That's exactly it. Thank you very much. 馃檪
Chris
On Wed, Jan 14, 2015 at 10:42 AM, Masaru Hasegawa [haniomasali@gmail.com](mailto:haniomasali@gmail.com)
wrote:
> Hi Chris,
>
> I think you hit this issue
> [Merge policy settings are ignored when set in YML 路 Issue #8890 路 elastic/elasticsearch 路 GitHub](https://github.com/elasticsearch/elasticsearch/issues/8890).
> Workaround would be to use index template (as described in the issue) or
> to update them by indices settings API.
>
> Masaru
>
> On Wed, Jan 14, 2015 at 9:52 AM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net)
> wrote:
>
> > Hi all.
> >
> > I'm reposting an earlier thread of mine with a more appropriate subject
> > in hopes that someone might have an idea on this one. 馃檪
> >
> > Each node in my cluster has its configuration set via elasticsearch.yml
> > only. I do not apply any index level settings, however the nodes in the
> > cluster are overwriting my config settings with the defaults. I have been
> > unable to figure out why this is happening, and was hoping someone else
> > might.
> >
> > My elasticsearch.yml file defines these settings:
> >
> > index:
> > codec:
> > bloom:
> > load: false
> > merge:
> > policy:
> > max\_merge\_at\_once: 4
> > max\_merge\_at\_once\_explicit: 4
> > max\_merged\_segment: 1gb
> > segments\_per\_tier: 4
> > type: tiered
> > scheduler:
> > max\_thread\_count: 1
> > type: concurrent
> > number\_of\_replicas: 0
> > number\_of\_shards: 1
> > refresh\_interval: 5s
> >
> > From the head plugin, I can see these settings are in effect:
> >
> > - settings: {
> > - index: {
> > - codec: {
> > - bloom: {
> > - load: false
> > }
> > }
> > - number\_of\_replicas: 1
> > - number\_of\_shards: 6
> > - translog: {
> > - flush\_threshold\_size: 1GB
> > }
> > - search: {
> > - slowlog: {
> > - threshold: {
> > - fetch: {
> > - warn: 2s
> > - info: 1s
> > }
> > - index: {
> > - warn: 10s
> > - info: 5s
> > }
> > - query: {
> > - warn: 10s
> > - info: 5s
> > }
> > }
> > }
> > }
> > - refresh\_interval: 60s
> > - merge: {
> > - scheduler: {
> > - type: concurrent
> > - max\_thread\_count: 1
> > }
> > - policy: {
> > - type: tiered
> > - max\_merged\_segment: 1gb
> > - max\_merge\_at\_once\_explicit: 4
> > - max\_merge\_at\_once: 4
> > - segments\_per\_tier: 4
> > }
> > }
> > }
> > - bootstrap: {
> > - mlockall: true
> > }
> > -
> >
> > But each node outputs this on new index creation:
> >
> > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > [elasticsearch-test] [test-20150113][1] updating [segments\_per\_tier] from
> > [4.0] to [10.0]
> > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > [elasticsearch-test] [test-20150113][1] updating [max\_merge\_at\_once] from
> > [4] to [10]
> > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > [elasticsearch-test] [test-20150113][1] updating
> > [max\_merge\_at\_once\_explicit] from [4] to [30]
> > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > [elasticsearch-test] [test-20150113][1] updating [max\_merged\_segment] from
> > [1024.0mb] to [5gb]
> >
> > This is happening both on two clusters for me. My "regular" ES cluster
> > of 3 nodes, and my dedicated Marvel cluster of 1 node. So strange.
> >
> > [2015-01-06 04:04:53,320][INFO][cluster.metadata]
> > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06] update\_mapping
> > [cluster\_state] (dynamic)
> > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > [segments\_per\_tier] from [4.0] to [10.0]
> > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > [max\_merge\_at\_once] from [4] to [10]
> > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > [max\_merge\_at\_once\_explicit] from [4] to [30]
> > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > [max\_merged\_segment] from [1024.0mb] to [5gb]
> >
> > I am really stumped on why this is happening!
> > Thanks so much for your time.
> > Chris
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > To view this discussion on the web visit
> > [https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com)
> > [https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com?utm_medium=email&utm_source=footer)
> > .
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug\_ETVoFwpY\_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug_ETVoFwpY_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com)
> [https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug\_ETVoFwpY\_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug_ETVoFwpY_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com?utm_medium=email&utm_source=footer)
> .
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAND3DpgX4J8zp0T6FgKseGNF1oAj%3D8\_gZh9pYWXa4Ag9UNbidQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3DpgX4J8zp0T6FgKseGNF1oAj%3D8_gZh9pYWXa4Ag9UNbidQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Chris\_Neal](https://discuss.elastic.co/u/Chris_Neal)
#### Post date: [January 20, 2015, 3:37am UTC](https://discuss.elastic.co/t/mysterious-index-settings-overwriting-cluster-settings/21622/4 "2015-01-20T03:37:53Z")
I'm a bit confused on the github page which versions have the bug, and
which do not. It has labels of:
1.4.3
1.5.0
2.0.0
My hunch is those versions do not have the bug, although it sure seems more
logical to tag versions that _do_ have the bug, so I wanted to confirm 馃檪
Thanks!
Chris
On Wed, Jan 14, 2015 at 11:07 AM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net)
wrote:
> Hi Masaru,
>
> Beautiful! That's exactly it. Thank you very much. 馃檪
>
> Chris
>
> On Wed, Jan 14, 2015 at 10:42 AM, Masaru Hasegawa [haniomasali@gmail.com](mailto:haniomasali@gmail.com)
> wrote:
>
> > Hi Chris,
> >
> > I think you hit this issue
> > [Merge policy settings are ignored when set in YML 路 Issue #8890 路 elastic/elasticsearch 路 GitHub](https://github.com/elasticsearch/elasticsearch/issues/8890).
> > Workaround would be to use index template (as described in the issue) or
> > to update them by indices settings API.
> >
> > Masaru
> >
> > On Wed, Jan 14, 2015 at 9:52 AM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net)
> > wrote:
> >
> > > Hi all.
> > >
> > > I'm reposting an earlier thread of mine with a more appropriate subject
> > > in hopes that someone might have an idea on this one. 馃檪
> > >
> > > Each node in my cluster has its configuration set via elasticsearch.yml
> > > only. I do not apply any index level settings, however the nodes in the
> > > cluster are overwriting my config settings with the defaults. I have been
> > > unable to figure out why this is happening, and was hoping someone else
> > > might.
> > >
> > > My elasticsearch.yml file defines these settings:
> > >
> > > index:
> > > codec:
> > > bloom:
> > > load: false
> > > merge:
> > > policy:
> > > max\_merge\_at\_once: 4
> > > max\_merge\_at\_once\_explicit: 4
> > > max\_merged\_segment: 1gb
> > > segments\_per\_tier: 4
> > > type: tiered
> > > scheduler:
> > > max\_thread\_count: 1
> > > type: concurrent
> > > number\_of\_replicas: 0
> > > number\_of\_shards: 1
> > > refresh\_interval: 5s
> > >
> > > From the head plugin, I can see these settings are in effect:
> > >
> > > - settings: {
> > > - index: {
> > > - codec: {
> > > - bloom: {
> > > - load: false
> > > }
> > > }
> > > - number\_of\_replicas: 1
> > > - number\_of\_shards: 6
> > > - translog: {
> > > - flush\_threshold\_size: 1GB
> > > }
> > > - search: {
> > > - slowlog: {
> > > - threshold: {
> > > - fetch: {
> > > - warn: 2s
> > > - info: 1s
> > > }
> > > - index: {
> > > - warn: 10s
> > > - info: 5s
> > > }
> > > - query: {
> > > - warn: 10s
> > > - info: 5s
> > > }
> > > }
> > > }
> > > }
> > > - refresh\_interval: 60s
> > > - merge: {
> > > - scheduler: {
> > > - type: concurrent
> > > - max\_thread\_count: 1
> > > }
> > > - policy: {
> > > - type: tiered
> > > - max\_merged\_segment: 1gb
> > > - max\_merge\_at\_once\_explicit: 4
> > > - max\_merge\_at\_once: 4
> > > - segments\_per\_tier: 4
> > > }
> > > }
> > > }
> > > - bootstrap: {
> > > - mlockall: true
> > > }
> > > -
> > >
> > > But each node outputs this on new index creation:
> > >
> > > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > > [elasticsearch-test] [test-20150113][1] updating [segments\_per\_tier] from
> > > [4.0] to [10.0]
> > > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > > [elasticsearch-test] [test-20150113][1] updating [max\_merge\_at\_once] from
> > > [4] to [10]
> > > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > > [elasticsearch-test] [test-20150113][1] updating
> > > [max\_merge\_at\_once\_explicit] from [4] to [30]
> > > [2015-01-13 02:12:52,062][INFO][index.merge.policy]
> > > [elasticsearch-test] [test-20150113][1] updating [max\_merged\_segment] from
> > > [1024.0mb] to [5gb]
> > >
> > > This is happening both on two clusters for me. My "regular" ES cluster
> > > of 3 nodes, and my dedicated Marvel cluster of 1 node. So strange.
> > >
> > > [2015-01-06 04:04:53,320][INFO][cluster.metadata]
> > > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06] update\_mapping
> > > [cluster\_state] (dynamic)
> > > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > > [segments\_per\_tier] from [4.0] to [10.0]
> > > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > > [max\_merge\_at\_once] from [4] to [10]
> > > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > > [max\_merge\_at\_once\_explicit] from [4] to [30]
> > > [2015-01-06 04:04:56,704][INFO][index.merge.policy]
> > > [elasticsearch-ip-10-0-0-42] [.marvel-2015.01.06][0] updating
> > > [max\_merged\_segment] from [1024.0mb] to [5gb]
> > >
> > > I am really stumped on why this is happening!
> > > Thanks so much for your time.
> > > Chris
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "elasticsearch" group.
> > > To unsubscribe from this group and stop receiving emails from it, send
> > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > > To view this discussion on the web visit
> > > [https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com)
> > > [https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAND3DphZTogfwqD992nDB8sRjNVq-01BbMRrd8UdGwB2hfUuYg%40mail.gmail.com?utm_medium=email&utm_source=footer)
> > > .
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > To view this discussion on the web visit
> > [https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug\_ETVoFwpY\_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug_ETVoFwpY_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com)
> > [https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug\_ETVoFwpY\_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAGmu3c2bi6EDqd7zkFjNWcug_ETVoFwpY_R3Qfh9rDXC0Q3wGQ%40mail.gmail.com?utm_medium=email&utm_source=footer)
> > .
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAND3DpipGddY7uCfkoMyk%2B8%3D7W4zu6KBhAwixSN0MmExD5Rcug%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3DpipGddY7uCfkoMyk%2B8%3D7W4zu6KBhAwixSN0MmExD5Rcug%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:37am UTC](https://discuss.elastic.co/t/mysterious-index-settings-overwriting-cluster-settings/21622/5 "2017-07-06T00:37:53Z")