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

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch tries to set a value for an index, but the provided value is not a number. This could be due to incorrect data type or a typo in the configuration file. To resolve this issue, ensure that the value you’re trying to set is a valid number. If it’s a configuration file issue, correct the typo or syntax error. If it’s a data type issue, convert the value to a number before setting it. Also, ensure that the field you’re trying to set is designed to accept numerical values.

This guide will help you check for common problems that cause the log ” failed to set [{}] for index [{}]; 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, index, metadata and settings.

Log Context

Log “failed to set [{}] for index [{}]; minimum value is not a number [{}]” classname is MetaDataUpdateSettingsService.java.
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 [{}] for index [{}]; minimum value is not a number [{}]";
                                e; IndexMetaData.SETTING_AUTO_EXPAND_REPLICAS; indexMetaData.getIndex(); sMin);
                        continue;
                    }
                    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?