Autoscaling policy with name ” + name + ” does not exist – Elasticsearch Error How To Solve Related Issues

Autoscaling policy with name ” + name + ” does not exist – 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 ” autoscaling policy with name ” + name + ” does not exist ” 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: plugin.

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”autoscaling policy with name [” + name + “] does not exist”classname  is TransportDeleteAutoscalingPolicyAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else {
  // we will reject the request below when we try to look up the policy by name
  currentMetadata = AutoscalingMetadata.EMPTY;
  }
  if (currentMetadata.policies().containsKey(name) == false) {
  throw new ResourceNotFoundException("autoscaling policy with name [" + name + "] does not exist");
  }
  final SortedMap newPolicies = new TreeMap(currentMetadata.policies());
  final AutoscalingPolicyMetadata policy = newPolicies.remove(name);
  assert policy != null : name;
  logger.info("deleting autoscaling policy [{}]"; name);

 

Optimize Elasticsearch Performance

Try The Tool