# Reloading elasticsearch.yml on ELK Stack

**URL:** <https://discuss.elastic.co/t/reloading-elasticsearch-yml-on-elk-stack/178649>\
**Category:** Elasticsearch\
**Created:** [April 26, 2019, 1:19pm UTC](https://discuss.elastic.co/t/reloading-elasticsearch-yml-on-elk-stack/178649 "2019-04-26T13:19:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johnnie843](https://avatars.discourse-cdn.com/v4/letter/j/53a042/32.png) [@Johnnie843](https://discuss.elastic.co/u/Johnnie843)\
**Post date:** [April 26, 2019, 1:19pm UTC](https://discuss.elastic.co/t/reloading-elasticsearch-yml-on-elk-stack/178649/1 "2019-04-26T13:19:36Z")

</div>

I made a change to my configuration on the elastic search side of the ELK stack. What is the proper sequence of events to reload the configuration without causing issues to the stack? Far as downtime, I need to keep it minimal but the stack can do down for a short period of time.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 26, 2019, 3:24pm UTC](https://discuss.elastic.co/t/reloading-elasticsearch-yml-on-elk-stack/178649/2 "2019-04-26T15:24:06Z")

</div>

You can perform a rolling restart, which is just like a [rolling upgrade](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html) except you skip the steps where you upgrade anything.

---

<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:** [May 24, 2019, 3:24pm UTC](https://discuss.elastic.co/t/reloading-elasticsearch-yml-on-elk-stack/178649/3 "2019-05-24T15:24:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.