# Unnecessary(?) shard reallocation upon adding warm nodes

**URL:** <https://discuss.elastic.co/t/unnecessary-shard-reallocation-upon-adding-warm-nodes/370782>\
**Category:** Elasticsearch\
**Created:** [November 19, 2024, 5:26pm UTC](https://discuss.elastic.co/t/unnecessary-shard-reallocation-upon-adding-warm-nodes/370782 "2024-11-19T17:26:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Field](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matt_field/32/130951_2.png) [@Matt\_Field](https://discuss.elastic.co/u/Matt_Field)\
**Post date:** [November 19, 2024, 5:26pm UTC](https://discuss.elastic.co/t/unnecessary-shard-reallocation-upon-adding-warm-nodes/370782/1 "2024-11-19T17:26:36Z")

</div>

On my [elastic.co](http://elastic.co) hosted cluster, i had 3 hot nodes with around 80% disk usage. I decided to add 2 warm nodes with **no modification** to the hot nodes configuration(i still have 3). Before creating the new warm nodes, elastic cloud carries out a task "performing a rolling change" which took about 1 hour (see screen shot below) which appeared to consist of trying to move all of the shards off each of the hot nodes in turn onto the other 2 hot nodes until they exceed the 93% disk watermark, turning my cluster red and loosing data in the process. Finally the warm nodes were created, but i dont understand why it needs to try to move all shards around when all i want to do is add a new node?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/2/72d36cc7f11ad293f42461d8cec40a47a70e3a89.png)