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

Average Read Time

2 Mins

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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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());

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content