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 run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and metadata.

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




 

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?

Analyze your cluster & get personalized recommendations

Skip to content