Failed to set minimum value is not a number – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.3-1.3

Briefly, this error occurs when Elasticsearch tries to set a minimum value for a field, but the provided value is not a number. This could be due to incorrect data types in the input or a misconfiguration in the mapping. To resolve this issue, ensure that the input data is of the correct numerical type. If the error persists, check the field mapping in your index settings. Make sure that the field is correctly mapped as a numerical type (integer, float, etc.). If necessary, reindex your data with the correct mapping.

This guide will help you check for common problems that cause the log ” failed to set [{}]; minimum value is not a number [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, metadata and settings.

Log Context

Log “failed to set [{}]; minimum value is not a number [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    final String sMin = autoExpandReplicas.substring(0; dash);
                    try {
                        min = Integer.parseInt(sMin);
                    } catch (NumberFormatException e) {
                        logger.warn("failed to set [{}]; minimum value is not a number [{}]";
                                e; IndexMetaData.SETTING_AUTO_EXPAND_REPLICAS; sMin);
                    String sMax = autoExpandReplicas.substring(dash + 1);
                    if (sMax.equals(ALL_NODES_VALUE)) {


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?