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

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

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide run our Elasticsearch Check-Up it analyses ES configuration to provide personalized recommendations that can solve many errors


To troubleshoot log “Failed to set . minimum value is not a number” it’s important to understand a few problems related to Elasticsearch concepts cluster, metadata, settings. See bellow important tips and explanations on these concepts

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 pro-actively troubleshoots, optimizes, automates and assists in what’s needed to successfully run Elasticsearch in production – hit the intercom button for more info on how to revolutionize your ES operation

Find Configuration Errors

Analyze Now