Ratio should be in 0-1.0; got – How to solve this Elasticsearch error

Average Read Time

2 Mins

Ratio should be in 0-1.0; got – How to solve this Elasticsearch error

Opster Team

July-20, 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 ” Ratio should be in 0-1.0; got ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

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 “Ratio should be in [0-1.0]; got [{}]”classname  is RatioValue.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 } else {
 try {
 double ratio = Double.parseDouble(sValue);
 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);
 }

 

Watch a demo of the Check-Up:

Analyze your cluster