# (bump) shards constantly relocating

**URL:** <https://discuss.elastic.co/t/bump-shards-constantly-relocating/354966>\
**Category:** Elasticsearch\
**Created:** [March 7, 2024, 3:17pm UTC](https://discuss.elastic.co/t/bump-shards-constantly-relocating/354966 "2024-03-07T15:17:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![raymondmintz11](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@raymondmintz11](https://discuss.elastic.co/u/raymondmintz11)\
**Post date:** [March 7, 2024, 3:25pm UTC](https://discuss.elastic.co/t/bump-shards-constantly-relocating/354966/5 "2024-03-07T15:25:49Z")

</div>

hi again,  
so i found this in my search, looks like the scenario is different though: no upgrade or high watermark issues in my use case:

> [@Cluster shards unbalanced and keep moving shards around after upgrade to 8.8.1](https://discuss.elastic.co/t/cluster-shards-unbalanced-and-keep-moving-shards-around-after-upgrade-to-8-8-1/336573/17):
>
> Hello @DavidTurner, There was another issue, a couple of the nodes were hitting the watermarks and others were close to it, so probably any shard movement could trigger another watermark that would then trigger another shard movement. I removed some old data to make sure that no node in the warm tier would hit any watermark, and after sometime there are no more shard movements. $ cat desired-balance.json | grep "node\_is\_desired" | grep -v relocating | grep false | wc -l 0

Is there a post somewhere you can reference ?

---

_[View the full topic](https://discuss.elastic.co/t/bump-shards-constantly-relocating/354966)._
