Briefly, this error occurs when Elasticsearch detects that the cluster’s capacity could be reduced without impacting performance. This is typically due to over-provisioning of resources. To resolve this, you can consider scaling down your cluster by reducing the number of nodes or decreasing the hardware specifications of your nodes. However, before making any changes, it’s crucial to thoroughly analyze your cluster’s usage patterns and ensure that the reduced capacity will still meet your needs, especially during peak usage times.
This guide will help you check for common problems that cause the log ” {} Calculated potential scaled down capacity [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “{} Calculated potential scaled down capacity [{}] ” classname is MlAutoscalingDeciderService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
+ " To allow a scale down [%s] must be increased.";
totalAssignedJobs;
MAX_OPEN_JOBS_PER_NODE.getKey();
maxOpenJobs;
MAX_OPEN_JOBS_PER_NODE.getKey());
logger.info(() -> new ParameterizedMessage("{} Calculated potential scaled down capacity [{}] ";
msg;
scaleDownDecisionResult.requiredCapacity()));
return new AutoscalingDeciderResult(context.currentCapacity(); reasonBuilder.setSimpleReason(msg).build());
}
}
[ratemypost]
