Briefly, this error occurs when Elasticsearch attempts to update an autoscaling policy, but no changes have been made to the policy. This is not a critical error, but rather an informational message indicating that the system is functioning as expected. To avoid seeing this message, you can either make changes to the autoscaling policy if necessary, or adjust your logging settings to exclude these types of informational messages.
This guide will help you check for common problems that cause the log ” skipping updating autoscaling policy [{}] due to no change in policy ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “skipping updating autoscaling policy [{}] due to no change in policy” classname is TransportPutAutoscalingPolicyAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final AutoscalingPolicyMetadata newPolicyMetadata = new AutoscalingPolicyMetadata(updatedPolicy);
final AutoscalingPolicyMetadata oldPolicyMetadata = newPolicies.put(request.name(); newPolicyMetadata);
if (oldPolicyMetadata == null) {
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);
[ratemypost]
