# Restart elasticsearch daemon necessarily?

**URL:** <https://discuss.elastic.co/t/restart-elasticsearch-daemon-necessarily/152348>\
**Category:** Elasticsearch\
**Created:** [October 13, 2018, 5:12pm UTC](https://discuss.elastic.co/t/restart-elasticsearch-daemon-necessarily/152348 "2018-10-13T17:12:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pauldon2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pauldon2/32/32079_2.png) [@pauldon2](https://discuss.elastic.co/u/pauldon2)\
**Post date:** [October 13, 2018, 5:12pm UTC](https://discuss.elastic.co/t/restart-elasticsearch-daemon-necessarily/152348/1 "2018-10-13T17:12:13Z")

</div>

Is it possible to force elasticsearch to change the configuration without restarting the service?

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [October 13, 2018, 7:27pm UTC](https://discuss.elastic.co/t/restart-elasticsearch-daemon-necessarily/152348/2 "2018-10-13T19:27:51Z")

</div>

No, this is not possible. Changes to the Elasticsearch configuration file are not picked up without a restart of the process.

---

<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:** [November 10, 2018, 7:27pm UTC](https://discuss.elastic.co/t/restart-elasticsearch-daemon-necessarily/152348/3 "2018-11-10T19:27:55Z")

</div>

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