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

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “setting with value is missing units; assuming default units () but in future versions this will be a hard error” it’s important to understand common problems related to Elasticsearch concepts: cluster, metadata. See detailed explanations below complete with common problems, examples and useful tips.

Metadata in Elasticsearch

What it is

Metadata in Elasticsearch refers to storing some additional information for each document. This is achieved using the specific metadata fields available in Elasticsearch. The default behavior of some of these metadata fields can be customized during mapping creation.

Examples

Using _meta meta-field for storing application-specific information with the mapping:

PUT /my_index?pretty
{
  "mappings": {
    "_meta": { 
      "domain": "security",
      "release_information": {
        "date": "18-01-2020",
        "version": "7.5"
      }
    }
  }
}

Notes
  • In version 2.x, Elasticsearch had a total 13 meta fields available, which are: _index, _uid, _type, _id, _source, _size, _all, _field_names, _timestamp, _ttl, _parent, _routing, _meta
  • In version 5.x, _timestamp and _ttl meta fields were removed.
  • In version 6.x, the _parent meta field was removed.
  • In version 7.x, _uid and _all meta fields were removed.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Request Was Aborted Could Not Crea  

2T Is A Nullreferenceexception And H  


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 have extracted the following from Elasticsearch source code to get 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






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster