# Shard recovery in 8.10.2 seems to happen more often

**URL:** <https://discuss.elastic.co/t/shard-recovery-in-8-10-2-seems-to-happen-more-often/357024>\
**Category:** Elasticsearch\
**Created:** [April 8, 2024, 10:53pm UTC](https://discuss.elastic.co/t/shard-recovery-in-8-10-2-seems-to-happen-more-often/357024 "2024-04-08T22:53:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [April 9, 2024, 8:43pm UTC](https://discuss.elastic.co/t/shard-recovery-in-8-10-2-seems-to-happen-more-often/357024/5 "2024-04-09T20:43:25Z")

</div>

> [@linkerc](#):
>
> I'll keep it at 30 to see if it's simply too many for the default of 2 to catch up.

You should use the default, there is an open issue about this, increasing this value can impact in the rebalance.

Check this issue: [Increasing `cluster.routing.allocation.cluster_concurrent_rebalance` causes redundant shard movements · Issue #87279 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/87279)

And also this one tracking a possible fix: [Throttle recoveries on data nodes instead of master · Issue #98087 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/98087)

> [@linkerc](#):
>
> We do create/delete some indices hourly & daily, but version 7.15 suggests our pattern of usage was not an issue for older algorithm.

There was also a change on version 8.6 that changed some things regarding balancing.

I had some issues when I upgraded to 8.8.1 about shards that kept moving around, as mentioned in this [topic](https://discuss.elastic.co/t/cluster-shards-unbalanced-and-keep-moving-shards-around-after-upgrade-to-8-8-1/336573).

---

_[View the full topic](https://discuss.elastic.co/t/shard-recovery-in-8-10-2-seems-to-happen-more-often/357024)._