# Indices in red state. "cannot allocate because all found copies of the shard are either stale or corrupt"
**URL:** https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871
**Category:** Elasticsearch
**Created:** [March 29, 2023, 10:29pm UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871 "2023-03-29T22:29:08Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@Bhuvesh\_Seth](https://discuss.elastic.co/u/Bhuvesh_Seth)
#### Post date: [March 29, 2023, 10:29pm UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/1 "2023-03-29T22:29:08Z")
Hi, we are facing one issue where some of indices health not getting updated to yellow or green due to this error "cannot allocate because all found copies of the shard are either stale or corrupt". Can someone please guide how to fix this issue without any data loss.
we tried reroute api with retry\_failed=true but that didn't work.
We are using Elasticsearch version 6.2.3
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [March 29, 2023, 10:33pm UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/2 "2023-03-29T22:33:03Z")
Please share more of the response you are getting.
> [@Bhuvesh\_Seth](#):
>
> We are using Elasticsearch version 6.2.3
Please note that version is [EOL](https://www.elastic.co/support/eol) and no longer supported, you should be looking to upgrade as a matter of urgency.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 29, 2023, 10:33pm UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/3 "2023-03-29T22:33:03Z")
Elasticsearch version 6.2.3 is [EOL](https://www.elastic.co/support/eol) and no longer supported. Please upgrade ASAP.
(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )
---
### Author:  [@Bhuvesh\_Seth](https://discuss.elastic.co/u/Bhuvesh_Seth)
#### Post date: [March 29, 2023, 10:58pm UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/4 "2023-03-29T22:58:11Z")
{
"index" : "IndexName",
"shard" : 0,
"primary" : true,
"current\_state" : "unassigned",
"unassigned\_info" : {
"reason" : "NODE\_LEFT",
"at" : "2023-03-26T06:26:40.845Z",
"details" : "node\_left[kKhS\_E7FQDS\_xVaLZTs4gg]",
"last\_allocation\_status" : "no\_valid\_shard\_copy"
},
"can\_allocate" : "no\_valid\_shard\_copy",
"allocate\_explanation" : "cannot allocate because all found copies of the shard are either stale or corrupt"
"node\_allocation\_decisions" : [
{
"node\_id" : "22l8b-PaTAey6kfuWsx9uQ",
"node\_name" : "node-c007-data-vm6",
"transport\_address" : "10.7.11.16:9300",
"node\_decision" : "no",
"store" : {
"found" : false
}
},
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [March 29, 2023, 11:10pm UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/5 "2023-03-29T23:10:41Z")
Is that node no longer part of the cluster? Do you have a replica?
---
### Author:  [@Bhuvesh\_Seth](https://discuss.elastic.co/u/Bhuvesh_Seth)
#### Post date: [March 30, 2023, 1:33am UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/6 "2023-03-30T01:33:21Z")
that node is part of cluster. We do have replica copy of same index but that shows the status as cluster\_Recovered.
---
### Author:  [@Bhuvesh\_Seth](https://discuss.elastic.co/u/Bhuvesh_Seth)
#### Post date: [March 30, 2023, 1:34am UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/7 "2023-03-30T01:34:15Z")
Sorry, what do you mean by replica? Replica shard. right?
---
### Author:  [@Bhuvesh\_Seth](https://discuss.elastic.co/u/Bhuvesh_Seth)
#### Post date: [March 31, 2023, 4:55pm UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/8 "2023-03-31T16:55:40Z")
can someone please help fix this issue?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [April 4, 2023, 1:28am UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/9 "2023-04-04T01:28:56Z")
What's the output from this;
```auto
GET /_cluster/allocation/explain?pretty
{
"index": "IndexName",
"shard": 0,
"primary": false
}
```
---
### Author:  [@Bhuvesh\_Seth](https://discuss.elastic.co/u/Bhuvesh_Seth)
#### Post date: [April 13, 2023, 2:43am UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/10 "2023-04-13T02:43:25Z")
> [@Bhuvesh\_Seth](#):
>
> cannot allocate because all found copies of the shard are either stale or corrupt
Sorry for late reply.
Here is the result I got.
primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"UnTTeuAkQsW\_Qt\_fyfiP1Q","node\_name":"_._._-c007-data-vm13","transport\_address":"_._._.18:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"Y916v1p1SIaOwhTcBGqHDQ","node\_name":"_._._-c007-data-vm11","transport\_address":"_._._.20:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"\_25POYZISYaZkdUNAW0hfQ","node\_name":"_._._-c007-data-vm8","transport\_address":"_._._.14:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"in7cl1tERVapS5n6EofsrQ","node\_name":"_._._-c007-data-vm3","transport\_address":"_._._.12:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"jtFs4rt3S\_e4VB6TSAhn1Q","node\_name":"_._._-c007-data-vm16","transport\_address":"_._._.10:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"kKhS\_E7FQDS\_xVaLZTs4gg","node\_name":"_._._-c007-data-vm10","transport\_address":"_._._.22:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"THROTTLE","explanation":"reached the limit of incoming shard recoveries [2], cluster setting [cluster.routing.allocation.node\_concurrent\_incoming\_recoveries=2] (can also be set via [cluster.routing.allocation.node\_concurrent\_recoveries])"}]},{"node\_id":"tE8ueSj9TgeyapbURZqnMw","node\_name":"_._._-c007-data-vm19","transport\_address":"_._._.23:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"ujM8E509TvysjIAbyslefQ","node\_name":"_._._-c007-data-vm15","transport\_address":"_._._.13:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"wlE49OBsSnubzwCYlOQH2A","node\_name":"_._._-c007-data-vm4","transport\_address":"_._._.17:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]},{"node\_id":"xh21XA3\_TzmsaamYMdZihQ","node\_name":"_._._-c007-data-vm5","transport\_address":"_._._.11:9300","node\_decision":"no","deciders":[{"decider":"replica\_after\_primary\_active","decision":"NO","explanation":"primary shard for this replica is not yet active"},{"decider":"throttling","decision":"NO","explanation":"primary shard for this replica is not yet active"}]}]}
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [April 13, 2023, 6:20am UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/11 "2023-04-13T06:20:08Z")
> [@Bhuvesh\_Seth](#):
>
> Can someone please guide how to fix this issue without any data loss.
If all primaries and replicas are corrupted I am not sure that is possible. I would recommend [reverting to a recent snapshot](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/snapshots-restore-snapshot.html).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 11, 2023, 6:20am UTC](https://discuss.elastic.co/t/indices-in-red-state-cannot-allocate-because-all-found-copies-of-the-shard-are-either-stale-or-corrupt/328871/12 "2023-05-11T06:20:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.