Unable to parse = as either percentage or bytes – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.13-8.9

Briefly, this error occurs when Elasticsearch is unable to interpret a value as either a percentage or bytes. This is usually due to incorrect formatting or syntax in the configuration file or request body. To resolve this issue, you should first check the syntax of your configuration file or request body. Ensure that the value you’re trying to parse is correctly formatted as a percentage or bytes. If the error persists, consider changing the value to a different format that Elasticsearch can interpret.

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” class name is RelativeByteSizeValue.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 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) {


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?