# High load issues on node (related to shard allocation)

**URL:** <https://discuss.elastic.co/t/high-load-issues-on-node-related-to-shard-allocation/320922>\
**Category:** Elasticsearch\
**Created:** [December 9, 2022, 7:33pm UTC](https://discuss.elastic.co/t/high-load-issues-on-node-related-to-shard-allocation/320922 "2022-12-09T19:33:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Russell\_Fulton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/russell_fulton/32/62888_2.png) [@Russell\_Fulton](https://discuss.elastic.co/u/Russell_Fulton)\
**Post date:** [December 9, 2022, 7:33pm UTC](https://discuss.elastic.co/t/high-load-issues-on-node-related-to-shard-allocation/320922/1 "2022-12-09T19:33:59Z")

</div>

I have a "warm" node with spinning disks which is experiencing high loads due to io waits. The problem is that some very active hot ingestion shards are being allocated to this node.

Is there anyway I can stop ES from allocating shards from hot indexes to this node?

---

<div class="post-metadata">

**Author:** ![Russell\_Fulton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/russell_fulton/32/62888_2.png) [@Russell\_Fulton](https://discuss.elastic.co/u/Russell_Fulton)\
**Post date:** [December 10, 2022, 10:01pm UTC](https://discuss.elastic.co/t/high-load-issues-on-node-related-to-shard-allocation/320922/2 "2022-12-10T22:01:30Z")

</div>

`index.routing.allocation.include._tier` seems to do the trick.

---

<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:** [January 7, 2023, 10:02pm UTC](https://discuss.elastic.co/t/high-load-issues-on-node-related-to-shard-allocation/320922/3 "2023-01-07T22:02:28Z")

</div>

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