# Unassigned shards - problem (does not recover / assign)

**URL:** <https://discuss.elastic.co/t/unassigned-shards-problem-does-not-recover-assign/217022>\
**Category:** Elasticsearch\
**Created:** [January 29, 2020, 2:44pm UTC](https://discuss.elastic.co/t/unassigned-shards-problem-does-not-recover-assign/217022 "2020-01-29T14:44:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rysiu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rysiu/32/61919_2.png) [@Rysiu](https://discuss.elastic.co/u/Rysiu)\
**Post date:** [January 29, 2020, 2:44pm UTC](https://discuss.elastic.co/t/unassigned-shards-problem-does-not-recover-assign/217022/1 "2020-01-29T14:44:59Z")

</div>

Hi!

I have a problem with the Elasticsearch cluster.

After restarting one of the nodes (resizing partitions in virtualization) this node started normally.

Some shards on the node work good.

A few shards, however, have a problem.

I have the status "Yellow" of few indexes (I have a number of replicas = 1).

However, the cluster does not want to fix these shards.

How can I fix it?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 29, 2020, 2:58pm UTC](https://discuss.elastic.co/t/unassigned-shards-problem-does-not-recover-assign/217022/2 "2020-01-29T14:58:17Z")

</div>

Try this Cluster Allocation Explain API, see [https://www.elastic.co/guide/en/elasticsearch/reference/7.5/cluster-allocation-explain.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/cluster-allocation-explain.html)

---

<div class="post-metadata">

**Author:** ![Rysiu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rysiu/32/61919_2.png) [@Rysiu](https://discuss.elastic.co/u/Rysiu)\
**Post date:** [January 29, 2020, 5:42pm UTC](https://discuss.elastic.co/t/unassigned-shards-problem-does-not-recover-assign/217022/3 "2020-01-29T17:42:12Z")

</div>

Well....

> "explanation" : "cannot relocate primary shard from a node with version [7.5.2] to a node with older version [7.5.1]"

7.5.2 is not compatible with 7.5.1 / 7.5.0?  
It's normal?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 30, 2020, 2:26pm UTC](https://discuss.elastic.co/t/unassigned-shards-problem-does-not-recover-assign/217022/4 "2020-01-30T14:26:06Z")

</div>

you can run them in parallel, as querying and indexing works, but you should not do that permanently.

That allocation decider is currently just checking if the receiving node's version is smaller than the sender's version, and does not take major/minor versions into account.

Easiest thing would be to just get all nodes on the same version.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 27, 2020, 2:26pm UTC](https://discuss.elastic.co/t/unassigned-shards-problem-does-not-recover-assign/217022/5 "2020-02-27T14:26:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.