# Some settings in elasticsearch.yml are not being applied

**URL:** <https://discuss.elastic.co/t/some-settings-in-elasticsearch-yml-are-not-being-applied/77>\
**Category:** Elasticsearch\
**Created:** [April 30, 2015, 11:49pm UTC](https://discuss.elastic.co/t/some-settings-in-elasticsearch-yml-are-not-being-applied/77 "2015-04-30T23:49:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [April 30, 2015, 11:49pm UTC](https://discuss.elastic.co/t/some-settings-in-elasticsearch-yml-are-not-being-applied/77/1 "2015-04-30T23:49:59Z")

</div>

YAML treats indented objects below an unindented object as children of that entry ([http://yaml.org/spec/1.2/spec.html#id2777534](http://yaml.org/spec/1.2/spec.html#id2777534)). This can cause the parser to throw out entries that are indented after an unindented line, and that line itself. This can cause ES to come up with default settings incorrectly.

Users should remove all indenting on all lines in elasticsearch.yml. With those out, the config should parse correctly.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:16am UTC](https://discuss.elastic.co/t/some-settings-in-elasticsearch-yml-are-not-being-applied/77/2 "2017-07-06T00:16:23Z")

</div>