Updating autoscaling policy – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-8.9

Briefly, this error occurs when there’s an issue updating the autoscaling policy in Elasticsearch. This could be due to incorrect policy settings, insufficient permissions, or network connectivity issues. To resolve this, you can verify the policy settings for any errors, ensure the user has the necessary permissions to update the policy, and check the network connection. Additionally, ensure that the Elasticsearch cluster is running the correct version that supports autoscaling.

This guide will help you check for common problems that cause the log ” updating autoscaling policy [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “updating autoscaling policy [{}]” classname is TransportPutAutoscalingPolicyAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            logger.info("adding autoscaling policy [{}]"; request.name());
        } else if (oldPolicyMetadata.equals(newPolicyMetadata)) {
            logger.info("skipping updating autoscaling policy [{}] due to no change in policy"; request.name());
            return currentState;
        } else {
            logger.info("updating autoscaling policy [{}]"; request.name());
        final AutoscalingMetadata newMetadata = new AutoscalingMetadata(newPolicies);
        builder.metadata(Metadata.builder(currentState.getMetadata()).putCustom(AutoscalingMetadata.NAME; newMetadata).build());
        return builder.build();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?