Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.
Briefly, this error occurs when Elasticsearch tries to access a machine learning model with a specific model_id that doesn’t exist or isn’t recognized in the system. To resolve this issue, you can verify the model_id and ensure it’s correctly inputted. If the model_id is correct, check if the model has been properly trained and stored in Elasticsearch. If not, you may need to retrain and store the model. Also, ensure that the model is accessible and not deleted or moved from its original location.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” No known trained model with model_id [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “No known trained model with model_id [{}]” class name is ExceptionsHelper.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
public static ResourceNotFoundException missingModelDeployment(String deploymentId) {
return new ResourceNotFoundException("No known model deployment with id [{}]"; deploymentId);
} public static ResourceNotFoundException missingTrainedModel(String modelId) {
return new ResourceNotFoundException("No known trained model with model_id [{}]"; modelId);
} public static ResourceNotFoundException missingTrainedModel(String modelId; Exception cause) {
return new ResourceNotFoundException("No known trained model with model_id [{}]"; cause; modelId);
}
