Log Failed to set . minimum value is not a number – How To Solve Related Issues



Log Failed to set . minimum value is not a number – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0



Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Failed to set . minimum value is not a number” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, metadata, settings.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”failed to set [{}]; 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 [{}]; minimum value is not a number [{}]";
                                e; IndexMetaData.SETTING_AUTO_EXPAND_REPLICAS; sMin);
                        continue;
                    }
                    String sMax = autoExpandReplicas.substring(dash + 1);
                    if (sMax.equals(ALL_NODES_VALUE)) {




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1  

Github Issue Number 12366  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now