# Elasticsearch node specific settings

**URL:** <https://discuss.elastic.co/t/elasticsearch-node-specific-settings/192133>\
**Category:** Elasticsearch\
**Created:** [July 24, 2019, 8:43pm UTC](https://discuss.elastic.co/t/elasticsearch-node-specific-settings/192133 "2019-07-24T20:43:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eightnoteight](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eightnoteight/32/38526_2.png) [@eightnoteight](https://discuss.elastic.co/u/eightnoteight)\
**Post date:** [July 24, 2019, 8:43pm UTC](https://discuss.elastic.co/t/elasticsearch-node-specific-settings/192133/1 "2019-07-24T20:43:37Z")

</div>

Hi,

We maintain a hot-warm architecture and I have noticed when I'm trying to move the shards from hot nodes to warm nodes, during the initial phase the a few shards would be moving from hot to warm, but this used to trigger a rebalance within hot nodes and the shards which at the end has to be moved from hot to warm are also moving within hot nodes. Considering the network bandwidth this slows down our relocation time a lot.

Is it possible to set node specific settings like I want to use 0 for`node_concurrent_incoming_recoveries` on hot nodes and 20 on warm nodes

I've tried to find documentation regarding this but couldn't find any thing that could help in this case.

---

<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:** [August 21, 2019, 8:43pm UTC](https://discuss.elastic.co/t/elasticsearch-node-specific-settings/192133/2 "2019-08-21T20:43:41Z")

</div>

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