# Weird rebalancing strategy

**URL:** https://discuss.elastic.co/t/weird-rebalancing-strategy/285034
**Category:** Elasticsearch
**Created:** [September 23, 2021, 10:20pm UTC](https://discuss.elastic.co/t/weird-rebalancing-strategy/285034 "2021-09-23T22:20:42Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)
#### Post date: [September 25, 2021, 8:32pm UTC](https://discuss.elastic.co/t/weird-rebalancing-strategy/285034/3 "2021-09-25T20:32:56Z")

</div>

7.3.1  
Yes. I have increased the node and task counts like below.

```auto
PUT _cluster/settings
{
  "persistent":{
    "cluster.routing.allocation.node_concurrent_recoveries":10,
    "cluster.routing.allocation.cluster_concurrent_rebalance":60
  }
}

```

I make similar changes whenever I add new nodes to speed up the rebalancing. This is the first time I've seen such behavior where new nodes will never reach the shard count as others. The shard count on those new nodes just fluctuate up and down and I noticed one new node being on both the source and destination. It seems a wasted move.  
This is the first time we have increased the data node size to 25. With 21 data nodes and below, I have never seen this on the same version of ES (7.3.1)

---

_[View the full topic](https://discuss.elastic.co/t/weird-rebalancing-strategy/285034)._