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

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 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. 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 and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (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());

 

Optimize Elasticsearch Performance

Try The Tool