Recovery with same target already registered; waiting for – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” recovery with same target already registered; waiting for ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery and indices.


 
 

recovery

Overview

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 /<index>/_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

Examples

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"}}

 
 

indices

 
 

Log Context

Log “recovery with same target already registered; waiting for”classname  is PeerRecoverySourceService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

*/
 synchronized Tuple addNewRecovery(StartRecoveryRequest request;
 IndexShard shard) {
 for (RecoverySourceHandler existingHandler : recoveryHandlers.keySet()) {
 if (existingHandler.getRequest().targetAllocationId().equals(request.targetAllocationId())) {
 throw new DelayRecoveryException("recovery with same target already registered; waiting for " +
 "previous recovery attempt to be cancelled or completed");
 }
 }
 final Tuple handlers = createRecoverySourceHandler(request; shard);
 recoveryHandlers.put(handlers.v1(); handlers.v2());

 

See how you can use AutoOps to resolve issues


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Analyze Your Cluster
Or view the full platform AutoOps in action

Related Articles

Back to all articles
Skip to content