Briefly, this error occurs when Elasticsearch’s machine learning feature fails to calculate the memory requirement for an anomaly detection job. This could be due to insufficient resources, incorrect job configuration, or internal issues. To resolve this, you can try increasing the memory allocation for Elasticsearch, ensure the job configuration is correct, or restart the Elasticsearch service. If the problem persists, consider checking the Elasticsearch logs for more detailed error information.
This guide will help you check for common problems that cause the log ” [” + jobId + “] failed to calculate anomaly detector job established model memory requirement ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, memory.
Log Context
Log “[” + jobId + “] failed to calculate anomaly detector job established model memory requirement” classname is MlMemoryTracker.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
memoryRequirementByAnomalyDetectorJob.put(jobId; memoryRequirementBytes);
phaserListener.onResponse(memoryRequirementBytes);
}
};
e -> {
logger.error("[" + jobId + "] failed to calculate anomaly detector job established model memory requirement"; e);
setAnomalyDetectorJobMemoryToLimit(jobId; phaserListener);
}
);
} catch (Exception e) {
logger.error("[" + jobId + "] failed to calculate anomaly detector job established model memory requirement"; e);
