[Elasticsearch 7.6] How do I fix unassigned shards issue

Elastic Stack Elasticsearch
1

Hello,

I installed an elastic search cluster consists of 3 nodes. after data had been ingested to the cluster, the status of the cluster became yellow due to unassigned shards issue.

image
image775×362 8.25 KB

2

Use the cluster allocation explain API to determine why it is not getting allocated.

1 Like
3

Thank You @Christian_Dahlqvist

i executed the api and the result was

image
image887×283 54.6 KB

have i delete this index to make cluster health status green

4

What was the full explanation?

5

Many Thanks @Christian_Dahlqvist
please find all response

{
"index" : ".apm-agent-configuration",
"shard" : 0,
"primary" : false,
"current_state" : "unassigned",
"unassigned_info" : {
"reason" : "INDEX_CREATED",
"at" : "2020-04-19T09:57:52.709Z",
"last_allocation_status" : "no_attempt"
},
"can_allocate" : "no",
"allocate_explanation" : "cannot allocate because allocation is not permitted to any of the nodes",
"node_allocation_decisions" : [
{
"node_id" : "id1",
"node_name" : "server01",
"transport_address" : "ip01",
"node_attributes" : {
"ml.machine_memory" : "33567191040",
"ml.max_open_jobs" : "20",
"xpack.installed" : "true"
},
"node_decision" : "no",
"weight_ranking" : 1,
"deciders" : [
{
"decider" : "node_version",
"decision" : "NO",
"explanation" : "cannot allocate replica shard to a node with version [7.6.1] since this is older than the primary version [7.6.2]"
}
]
},
{
"node_id" : "id2",
"node_name" : "server02",
"transport_address" : "ip02",
"node_attributes" : {
"ml.machine_memory" : "33567191040",
"ml.max_open_jobs" : "20",
"xpack.installed" : "true"
},
"node_decision" : "no",
"weight_ranking" : 2,
"deciders" : [
{
"decider" : "node_version",
"decision" : "NO",
"explanation" : "cannot allocate replica shard to a node with version [7.6.1] since this is older than the primary version [7.6.2]"
}
]
},
{
"node_id" : "id03",
"node_name" : "server03",
"transport_address" : "ip03",
"node_attributes" : {
"ml.machine_memory" : "33567195136",
"ml.max_open_jobs" : "20",
"xpack.installed" : "true"
},
"node_decision" : "no",
"weight_ranking" : 3,
"deciders" : [
{
"decider" : "same_shard",
"decision" : "NO",
"explanation" : "the shard cannot be allocated to the same node on which a copy of the shard already exists [[.apm-agent-configuration][0], node[id03], [P], s[STARTED], a[id=-........]]"
}
]
}
]
}

6

You have mixed versions in your cluster which is interfering with the allocation. Please make sure all nodes are running EXACTLY the same version.

7

Thank You @Christian_Dahlqvist

i checked the three node

2 node with Elastisearch 7.6.1 version
1 node with Elastisearch 7.6.2 version

Please can you advise me how can i fix this issue without make production down .
where application is up running and it's critical situation

8

Do a rolling upgrade to 7.6.2

1 Like
9

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