Could not parse settings for model model – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

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 is unable to parse the settings for a specific model due to incorrect syntax, missing parameters, or invalid values. To resolve this issue, you should first verify the syntax of your settings, ensuring it adheres to the correct JSON format. Next, check that all required parameters are included and that their values are valid. If the error persists, consider resetting the settings to their default values and reconfiguring them one by one to identify the problematic setting.

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 ” Could not parse settings for model [” + model + “]. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations, settings, search.

Log Context

Log “Could not parse settings for model [” + model + “].” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 MovAvgModel movAvgModel;
 try {
 movAvgModel = modelParser.parse(settings; pipelineAggregatorName; factory.window());
 } catch (ParseException exception) {
 throw new ParsingException(parser.getTokenLocation(); "Could not parse settings for model [" + model + "]."; exception);
 if (minimize != null) {


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?

Get expert answers on Elasticsearch/OpenSearch