After a full cluster restart, some of my indices remained red. Among them a few had replicas... Cluster allocation explain API informs me that a pri 3 rep 1 index is missing its primary shard 0, on every node I get: "node_decision": "no", "store": { "found": false } Well…

[image] hunsw: "primary shard for this replica is not yet active" } Okay, this was very stupid on my part: one of the 20+ nodes was actually down. I trusted our automation system too much and didn't look close enough.

Cannot recover index - store.found: false

Elastic Stack Elasticsearch

hunsw (Attila) March 17, 2020, 2:10pm 13

Ok, thank you for your help, I guess we need further investigation how this could happen.

Topic		Replies	Views
Cannot allocate because a previous copy of the primary shard existed but can no longer be found on the nodes in the cluster Elasticsearch	9	16703	September 15, 2020
Shard recovery with only one node in the cluster Elasticsearch	3	655	July 6, 2017
[1.7.2] unassigned shards after restart for indexes with no replication Elasticsearch	7	1916	July 5, 2017
Lost shards and cluster state stays red Elasticsearch	3	5259	July 6, 2017
Unassigned primary shards not found Elasticsearch	1	383	July 5, 2017

Cannot recover index - store.found: false

Related topics