Mix of settings map and top-level properties – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8-8.9

Briefly, this error occurs when there’s a conflict between the settings map and top-level properties in the Elasticsearch configuration. This usually happens when both are defined in the same configuration file. To resolve this, you can either move all settings into the settings map or move all settings to top-level properties. Ensure that the same setting isn’t defined in both places. Also, check the Elasticsearch documentation to understand the correct format and hierarchy of settings.

This guide will help you check for common problems that cause the log ” mix of settings map and top-level properties ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: settings, admin, indices.

Log Context

Log “mix of settings map and top-level properties” class name is UpdateSettingsRequest.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 * will result in a parse exception being thrown.
 private static void checkMixedRequest(Map bodySettings) {
 assert bodySettings.containsKey("settings");
 if (bodySettings.size() > 1) {
 throw new ElasticsearchParseException("mix of settings map and top-level properties");
 }  @Override
 public String toString() {


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?