Log setting with value is missing units; assuming default units () but in future versions this will be a hard error – How To Solve Related Issues



Log setting with value is missing units; assuming default units () but in future versions this will be a hard error – 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 “setting with value is missing units; assuming default units () but in future versions this will be a hard error” 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.


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”{} setting [{}] with value [{}] is missing units; assuming default units ({}) but in future versions this will be a hard error” classname is MetaData.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             Long.parseLong(settingValue);
        } catch (NumberFormatException e) {
            return settingValue;
        }
        // It's a naked number that previously would be interpreted as default unit; now we add it:
        logger.warn("{} setting [{}] with value [{}] is missing units; assuming default units ({}) but in future versions this will be a hard error";
                unitName; settingName; settingValue; unit);
        return settingValue + unit;
    }

    /** As of 2.0 we require units for time and byte-sized settings. This methods adds default units to any




 

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 Request Was Aborted Could Not Crea  

T Is A Nullreferenceexception And H  

 

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