# No shard is getting assigned on one of the data node

**URL:** <https://discuss.elastic.co/t/no-shard-is-getting-assigned-on-one-of-the-data-node/292575>\
**Category:** Elasticsearch\
**Created:** [December 21, 2021, 2:21pm UTC](https://discuss.elastic.co/t/no-shard-is-getting-assigned-on-one-of-the-data-node/292575 "2021-12-21T14:21:27Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 21, 2021, 4:55pm UTC](https://discuss.elastic.co/t/no-shard-is-getting-assigned-on-one-of-the-data-node/292575/6 "2021-12-21T16:55:40Z")

</div>

> [@pratiksha](#):
>
> `dropping pending state [[uuid[p2MPdq59QCKtduezFv9Y2A], v[175229293], m[NAlqPclnQY-25G9p6_4mBA]]]. more than [25] pending states.`

This is pretty much the same thing as your [other thread](https://discuss.elastic.co/t/receiving-timed-out-waiting-for-all-nodes-to-process-published-state/291670) in which your cluster seems heavily overloaded and is running a very old version. You have less than 1MB of data but well over 1000 primary shards.

As [mentioned before](https://discuss.elastic.co/t/receiving-timed-out-waiting-for-all-nodes-to-process-published-state/291670/2), you should upgrade as a matter of some urgency. Newer versions will deal with high shard counts better, and also have better diagnostic tooling for working out what else might be going wrong.

In the meantime I expect it will help to delete any indices you don't need.

---

_[View the full topic](https://discuss.elastic.co/t/no-shard-is-getting-assigned-on-one-of-the-data-node/292575)._