Shards stuck in unassigned state

(Maddy M) #1


Cluster hit the circuit breaker, so we increased the limit temporarily.

  1. But we restart one of the node and that node is stuck at 500 shards and unable to move further into initialize other shards. There are multiple indices and multiple UNASSIGNED shards.
  2. Other node has 1650 shards and that node is health.
  3. I am using 6.4

Could you please let us know when this issue happening and advise for resolution?


(Brandon Hatch) #2

There has been a few times where after a node runs out of storage, some shards don't want to re-initialize after more storage has been added. In that situation closing the index, and then re-opening it fixed it for us. This was on earlier versions of ES though.

(Maddy M) #3

Hi Brandon,

Thanks for the advise. It is really helpful. I am able to see all the shards in both the nodes!!

Once again thanks.


(system) closed #4

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