Recovery with same target already registered; waiting for – Elasticsearch Error How To Solve Related Issues



Recovery with same target already registered; waiting for – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: recovery, indices.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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

 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 An item with the same key has already been added -views 350,271 ,score 135

Docker error : no space left on device -views   244,251,score 336

 

 

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now