Elasticsearch Recovery

Average Read Time

1 Mins

Elasticsearch Recovery

Opster Team

October 2021

Average Read Time

1 Mins

In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.

The Elasticsearch Check-Up is free and requires no installation.

Run the Elasticsearch check-up to receive recommendations like this:

checklist Run Check-Up

The following configuration error was detected on node 123...



This error can have a severe impact on your system. It's important to understand that it was caused by...



In order to resolve this issue and prevent it from occurring again, we recommend that you begin by changing the configuration to...


X-PUT curl -H "Content-Type: application/json" [customized recommendation]


In Elasticsearch, recovery refers to the process of recovering an index or shard when something goes wrong. There are many ways to recover an index or shard, such as by re-indexing the data from a backup / failover cluster to the current one, or by restoring from an Elasticsearch snapshot. Alternatively, Elasticsearch performs recoveries automatically, such as when a node restarts or disconnects and connects again. There is an API to check the updated status of index / shard recoveries.

GET //_recoveryGET /_recovery

In summary, recovery can happen in the following scenarios:

  • Node startup or failure (local store recovery)
  • Replication of primary shards to replica shards
  • Relocation of a shard to a different node in the same cluster
  • Restoring a snapshot


Getting recovery information about several indices:

GET my_index1
GET my_index2/_recovery

Notes and good things to know

  • When a node is disconnected from the cluster, all of its shards go to an unassigned state. After a certain amount of time, the shards will be allocated somewhere else on other nodes. This setting determines the number of concurrent shards per node that will be recovered.
PUT _cluster/settings{"transient":{"cluster.routing.allocation.node_concurrent_recoveries":3}}
  • You can also control when to start recovery after a node disconnects. This is useful if the node just restarts, for example, because you may not want to initiate any recovery for such transient events.
PUT _all/_settings{"settings":{"index.unassigned.node_left.delayed_timeout":"6m"}}
  • Elasticsearch limits the speed that is allocated to recovery in order to avoid overloading the cluster. This setting can be updated to make the recovery faster or slower, depending on your requirements.
PUT _cluster/settings{"transient":{"indices.recovery.max_bytes_per_sec":"100mb"}}

Related log errors to this ES concept

Error while listing local files; recovering as if there are none
Error while reading global checkpoint from translog;
Unexpected error while monitoring recovery
Delaying initial state recovery for .
Recovery failed
Unexpected error during recovery ; failing shard
Ignoring recovery of a corrupt translog entry
Snapshot differs from actual index for file: meta:
Remote file corruption on node ; recovering . local checksum OK
Releasing snapshot caused exception
Corrupted file detected checksum mismatch
Close engine failed

< Page: 1 of 4 >

Run the Check-Up to get a customized report like this:

Analyze your cluster