# Apply different settings per node role

**URL:** <https://discuss.elastic.co/t/apply-different-settings-per-node-role/369025>\
**Category:** Elasticsearch\
**Created:** [October 17, 2024, 7:54pm UTC](https://discuss.elastic.co/t/apply-different-settings-per-node-role/369025 "2024-10-17T19:54:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andy-w00d](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andy-w00d/32/138478_2.png) [@andy-w00d](https://discuss.elastic.co/u/andy-w00d)\
**Post date:** [October 17, 2024, 7:54pm UTC](https://discuss.elastic.co/t/apply-different-settings-per-node-role/369025/1 "2024-10-17T19:54:01Z")

</div>

I have a cluster with coordinating nodes that are relatively much smaller than data nodes - 4Gi vs 256Gi memory, respectively. I am starting to see indexing pressure rejections from the coordinating stage, only on the coordinating nodes. All of these coordinating nodes are using \<50% heap. I would like to increase `indexing_pressure.memory.limit` but only on these coordinating nodes as they have plenty of heap available. This does not seem possible as the setting is cluster-wide. Is there a workaround? I'd rather not scale up the coordinating nodes while there is still room in the heap.

---

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [October 18, 2024, 9:25am UTC](https://discuss.elastic.co/t/apply-different-settings-per-node-role/369025/2 "2024-10-18T09:25:08Z")

</div>

Hi @andy-w00d :

`indexing_pressure.memory.limit` is a node setting ([docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-indexing-pressure.html#memory-limits)). You should be able to specify this setting in your elasticsearch configuration.

Hope that helps!