Autoscaling policy with name ” + name + ” does not exist – 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 ” autoscaling policy with name ” + name + ” does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

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 “autoscaling policy with name [” + name + “] does not exist”classname  is 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;"deleting autoscaling policy [{}]"; name);


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content