Invalid ratio or percentage – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch receives an invalid ratio or percentage value in a request. This could be due to a typo, incorrect formatting, or a value outside the acceptable range. To resolve this issue, you should first check the request for any obvious mistakes. Ensure that the ratio or percentage is correctly formatted and within the acceptable range. If the error persists, you may need to debug your code to identify the source of the invalid value.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Invalid ratio or percentage [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “Invalid ratio or percentage [{}]” class name is RatioValue.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (ratio < 0 || ratio > 1.0) {
 throw new ElasticsearchParseException("Ratio should be in [0-1.0]; got [{}]"; ratio);
 }
 return new RatioValue(100.0 * Math.abs(ratio));
 } catch (NumberFormatException e) {
 throw new ElasticsearchParseException("Invalid ratio or percentage [{}]"; sValue);
 }  }
 }

 

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?