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

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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: .

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content