Unexpected error – How to solve this Elasticsearch error

Average Read Time

2 Mins

Unexpected error – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” unexpected error ” 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”unexpected error”classname  is PeerRecoveryTargetService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public void onFailure(Exception e) {
  try (RecoveryRef recoveryRef = onGoingRecoveries.getRecovery(recoveryId)) {
  if (recoveryRef != null) {
  logger.error(() -> new ParameterizedMessage("unexpected error during recovery [{}]; failing shard"; recoveryId); e);
  new RecoveryFailedException(recoveryRef.target().state(); "unexpected error"; e);
  true // be safe
  } else {
  logger.debug(() -> new ParameterizedMessage(
  "unexpected error during recovery; but recovery id [{}] is finished"; recoveryId); e);


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

Analyze your cluster