# How to make elasticsearch data node to read the config without restarting the data node?

**URL:** <https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751>\
**Category:** Elasticsearch\
**Created:** [March 17, 2016, 6:21pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751 "2016-03-17T18:21:51Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dany](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dany/32/8131_2.png) [@dany](https://discuss.elastic.co/u/dany)\
**Post date:** [March 17, 2016, 6:21pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/1 "2016-03-17T18:21:51Z")

</div>

In my use case I would like to change the no of shards in data node config. I want the data node to read the updated config without rebouncing. Is there a way to do that[an API call may be?]

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 17, 2016, 7:33pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/2 "2016-03-17T19:33:18Z")

</div>

I don't think that's possible, but you should control the number of shards for newly created indexes by other means than a static setting in elasticsearch.yml. Either specify it when an index is created or use an index template.

---

<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:** [March 17, 2016, 7:33pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/3 "2016-03-17T19:33:57Z")

</div>

The only way to pick up _config file_ changes is by bouncing the node.

You can control the number of shards via other means though such as the index settings (when you create the index), or via index templates.

---

<div class="post-metadata">

**Author:** ![dany](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dany/32/8131_2.png) [@dany](https://discuss.elastic.co/u/dany)\
**Post date:** [March 17, 2016, 10:04pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/4 "2016-03-17T22:04:12Z")

</div>

Thank you for the info. I have large amount of data. When I rebounce the process es might relocate shards from that node. That will affect the query performance. Is there any workaround for this?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 17, 2016, 10:18pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/5 "2016-03-17T22:18:13Z")

</div>

Nope.

---

<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:** [March 17, 2016, 10:19pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/6 "2016-03-17T22:19:12Z")

</div>

> [@dany](#):
>
> When I rebounce the process es might relocate shards from that node. That will affect the query performance. Is there any workaround for this?

You can use [delayed allocation](https://www.elastic.co/guide/en/elasticsearch/reference/2.2/delayed-allocation.html).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 17, 2016, 10:42pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/7 "2016-03-17T22:42:26Z")

</div>

It'll help with allocation, but it may not help with query performance.

---

<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 5, 2017, 11:07pm UTC](https://discuss.elastic.co/t/how-to-make-elasticsearch-data-node-to-read-the-config-without-restarting-the-data-node/44751/8 "2017-07-05T23:07:26Z")

</div>


