No shards assigning of an index on elastic version 2.X

We have 15 Nodes cluster where 3 master 12 data Nodes.
After hitting below comand
curl -XGET 'localhost:9200/_cat/shards?h=index,shard,prirep,state,unassigned.reason,unassigned.details'| grep UNASSIGNED

index1 2 r UNASSIGNED CLUSTER_RECOVERED
index1 3 p UNASSIGNED CLUSTER_RECOVERED
index1 3 r UNASSIGNED CLUSTER_RECOVERED
index1 4 p UNASSIGNED CLUSTER_RECOVERED
index1 4 r UNASSIGNED CLUSTER_RECOVERED
index1 1 p UNASSIGNED CLUSTER_RECOVERED
index1 1 r UNASSIGNED CLUSTER_RECOVERED
index1 0 p UNASSIGNED CLUSTER_RECOVERED
index1 0 r UNASSIGNED CLUSTER_RECOVERED
index2 2 p UNASSIGNED CLUSTER_RECOVERED
index2 2 r UNASSIGNED CLUSTER_RECOVERED
index2 3 p UNASSIGNED CLUSTER_RECOVERED
index2 3 r UNASSIGNED CLUSTER_RECOVERED
index2 4 p UNASSIGNED CLUSTER_RECOVERED
index2 4 r UNASSIGNED CLUSTER_RECOVERED
index2 1 p UNASSIGNED CLUSTER_RECOVERED
index2 1 r UNASSIGNED CLUSTER_RECOVERED
index2 0 p UNASSIGNED CLUSTER_RECOVERED
index2 0 r UNASSIGNED CLUSTER_RECOVERED
index3 2 p UNASSIGNED CLUSTER_RECOVERED
index3 2 r UNASSIGNED CLUSTER_RECOVERED
index3 3 p UNASSIGNED CLUSTER_RECOVERED
index3 3 r UNASSIGNED CLUSTER_RECOVERED
index3 4 p UNASSIGNED CLUSTER_RECOVERED
index3 4 r UNASSIGNED CLUSTER_RECOVERED
index3 1 p UNASSIGNED CLUSTER_RECOVERED
index3 1 r UNASSIGNED CLUSTER_RECOVERED
index3 0 p UNASSIGNED CLUSTER_RECOVERED
index3 0 r UNASSIGNED CLUSTER_RECOVERED

No logs are generated on regarding why cluster is not able to assign the above index

What happened to the cluster to get it into that state? There must surely be something in the logs? What type of hardware and storage are you using?

Thanks @Christian_Dahlqvist for the prompt response.
So one of the master node not responding from 2 days before, yesterday its we kill and started that node to join, When it joins the cluster, Cluster health becomes red. because of shared indices unassigned.
We try to close and opened mention indices and also try to restart whole cluster.

Below is the current specification

curl -XGET localhost:9200/_cat/allocation?v
shards disk.indices disk.used disk.avail disk.total disk.percent host ip node
342 201.6gb 226.8gb 265.1gb 492gb 46 10.1.2.92 10.1.2.92 dn7
342 212gb 234.4gb 257.5gb 492gb 47 10.1.2.85 10.1.2.85 dn1
341 214.3gb 239.5gb 252.4gb 492gb 48 10.1.2.93 10.1.2.93 dn8
343 200.8gb 226gb 266gb 492gb 45 10.1.2.74 10.1.2.74 10.1.2.74
342 199.6gb 225.5gb 266.5gb 492gb 45 10.1.2.217 10.1.2.217 dn5
342 212.3gb 234.2gb 257.7gb 492gb 47 10.1.2.89 10.1.2.89 dn2
343 215.7gb 241gb 251gb 492gb 48 10.1.2.240 10.1.2.240 10.1.2.240
342 195.4gb 217.4gb 274.5gb 492gb 44 10.1.2.134 10.1.2.134 dn3
342 213.8gb 239.1gb 252.9gb 492gb 48 10.1.2.101 10.1.2.101 10.1.2.101
343 223gb 248.2gb 243.7gb 492gb 50 10.1.2.250 10.1.2.250 10.1.2.250
342 206gb 231.1gb 260.8gb 492gb 46 10.1.2.91 10.1.2.91 dn6
341 212.9gb 238.7gb 253.2gb 492gb 48 10.1.2.140 10.1.2.140 dn4
30 UNASSIGNED

Side note, 2.X has been EOL for a long, long time. You should really upgrade :slight_smile:

1 Like

Elasticsearch 2.X is so old that the APIs I would usually use to troubleshoot are not available. I would agree with Mark and recommend an upgrade.

Are indices slowly recovering and initializing? What does the _cat/recovery API give?

As I have not used Elasticsearch 2.x in years I am not sure how much I will be able to help.