# Unassigned shards, with status "Elasticsearch can allocate the shard" for all of them **URL:** \ **Category:** Elasticsearch\ **Created:** [May 18, 2023, 7:30pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-status-elasticsearch-can-allocate-the-shard-for-all-of-them/333806 "2023-05-18T19:30:38Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Petr.Simik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/petr.simik/32/38082_2.png) [@Petr.Simik](https://discuss.elastic.co/u/Petr.Simik)\ **Post date:** [May 19, 2023, 9:49am UTC](https://discuss.elastic.co/t/unassigned-shards-with-status-elasticsearch-can-allocate-the-shard-for-all-of-them/333806/7 "2023-05-19T09:49:27Z")
Thank you, I will upgrade the cluster and will see. Do you think it might have common root cause with issue I have reported here yesterday: > [@Elastic shard balancing / allocation](https://discuss.elastic.co/t/elastic-shard-balancing-allocation/333713): > > Hi We are on Elastic 8.6 with 38 hot data nodes and ingesting about 140 different indices Top 10 indices have indexing rate about 15-50K events/sec. 20 indices has 1-20 K events/sec. And remaining 100 indices indexing in low rate 0-1000 of events/sec. All nodes have 8vcpu, 32GB RAM, 2TB SSD. As you can see in table below the cluster overflows some nodes and some are almost empty despite the fact that they all have the same capacity and performance could you help me with some ideas what I … it seem the cluster have problem with rebalancing process --- _[View the full topic](https://discuss.elastic.co/t/unassigned-shards-with-status-elasticsearch-can-allocate-the-shard-for-all-of-them/333806)._