# ERROR: no\_shard\_available\_action\_exception after restoring the snapshot
**URL:** https://discuss.elastic.co/t/error-no-shard-available-action-exception-after-restoring-the-snapshot/365021
**Category:** Elasticsearch
**Tags:** docker, snapshot-and-restore
**Created:** [August 16, 2024, 11:52am UTC](https://discuss.elastic.co/t/error-no-shard-available-action-exception-after-restoring-the-snapshot/365021 "2024-08-16T11:52:51Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@cassper](https://discuss.elastic.co/u/cassper)
#### Post date: [August 16, 2024, 11:52am UTC](https://discuss.elastic.co/t/error-no-shard-available-action-exception-after-restoring-the-snapshot/365021/1 "2024-08-16T11:52:51Z")
Hello,
I am using ES 8.13 docker and try to restore the snapshot.
I am using \_restore ES API.
```auto
_snapshot/my_repository/snapshot_1/_restore?wait_for_completion=true
{
"indices": "test-000001"
}
```
Result -
```auto
{
"snapshot": {
"snapshot": "snapshot_1",
"indices": [
"test-000001"
],
"shards": {
"total": 1,
"failed": 1,
"successful": 0
}
}
}
```
I checked the docker logs as well.
```auto
[T#2]","log.logger":"org.elasticsearch.snapshots.RestoreService","elasticsearch.cluster.uuid":"o9y_nhi1SfyEtlGKmhdLQQ","elasticsearch.node.id":"XtVeRwJLQdGjmqhxQ4nokg","elasticsearch.node.name":"elasticsearch","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2024-08-16T10:41:36.070Z", "log.level": "INFO", "current.health":"RED","message":"Cluster health status changed from [YELLOW] to [RED] (reason: [reconcile-desired-balance]).","previous.health":"YELLOW","reason":"reconcile-desired-balance" , "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch-81][masterService#updateTask][T#2]","log.logger":"org.elasticsearch.cluster.routing.allocation.AllocationService","elasticsearch.cluster.uuid":"o9y_nhi1SfyEtlGKmhdLQQ","elasticsearch.node.id":"XtVeRwJLQdGjmqhxQ4nokg","elasticsearch.node.name":"elasticsearch-81","elasticsearch.cluster.name":"docker-cluster"}
```
These are the indices what we have after restoring:
```auto
red open test-000001 xVK8undETUG75c58bxWBDQ 1 1
```
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [August 16, 2024, 1:47pm UTC](https://discuss.elastic.co/t/error-no-shard-available-action-exception-after-restoring-the-snapshot/365021/2 "2024-08-16T13:47:59Z")
See [this troubleshooting guide](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html) for further info.
---
### Author:  [@cassper](https://discuss.elastic.co/u/cassper)
#### Post date: [August 21, 2024, 12:48pm UTC](https://discuss.elastic.co/t/error-no-shard-available-action-exception-after-restoring-the-snapshot/365021/3 "2024-08-21T12:48:10Z")
> [@cassper](#):
>
> `test-000001`
```auto
/_cat/shards?v=true&h=index,shard,prirep,state,node,unassigned.reason&s=state
```
Result
```auto
index shard prirep state node unassigned.reason
test-000001 0 r UNASSIGNED NEW_INDEX_RESTORED
test-000001 0 p UNASSIGNED NEW_INDEX_RESTORED
```
```auto
_cluster/allocation/explain?filter_path=index,node_allocation_decisions.node_name,node_allocation_decisions.deciders.*
```
Result
```auto
{
"index": "test-000001",
"node_allocation_decisions": [
{
"node_name": "elasticsearch",
"deciders": [
{
"decider": "restore_in_progress",
"decision": "NO",
"explanation": "shard has failed to be restored from the snapshot [my_repository:snapshot_1/04TxOY85QaipfMx3f2e2ag] - manually close or delete the index [test-000001] in order to retry to restore the snapshot again or use the reroute API to force the allocation of an empty primary shard. Details: [restore_source[my_repository/snapshot_1]]"
},
{
"decider": "disk_threshold",
"decision": "NO",
"explanation": "the node is above the low watermark cluster setting [cluster.routing.allocation.disk.watermark.low=85%], having less than the minimum required [137gb] free space, actual free: [77.9gb], actual used: [91.4%]"
}
]
}
]
}
```
I tried with reroute API. but it didn't work.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [August 21, 2024, 4:40pm UTC](https://discuss.elastic.co/t/error-no-shard-available-action-exception-after-restoring-the-snapshot/365021/4 "2024-08-21T16:40:31Z")
> [@cassper](#):
>
> `the node is above the low watermark cluster setting`
This suggests you don't have enough disk space to restore the snapshot.