Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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.
Take a self-guided product tour to see for yourself (no registration required).This guide will help you check for common problems that cause the log ” unable to parse = as either percentage or bytes ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “unable to parse [{}={}] as either percentage or bytes”classname is RelativeByteSizeValue.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// ignore; see if it parses as bytes
}
try {
return new RelativeByteSizeValue(ByteSizeValue.parseBytesSizeValue(value; settingName));
} catch (ElasticsearchParseException e) {
throw new ElasticsearchParseException("unable to parse [{}={}] as either percentage or bytes"; e; settingName; value);
}
}
public String getStringRep() {
if (ratio != null) {
Find & fix Elasticsearch problems
