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 OpenSearch operation.
Briefly, this error occurs when the input value for a ratio or percentage in OpenSearch is not valid. This could be due to incorrect formatting, a value outside the acceptable range, or a non-numeric value. To resolve this issue, ensure that the input value is a number and within the acceptable range. If it’s a percentage, it should be between 0 and 100. If it’s a ratio, it should be between 0 and 1. Also, check for any syntax errors or misplaced decimal points.
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 OpenSearch concepts: .
Log Context
Log “Invalid ratio or percentage [{}]” class name is RatioValue.java. We extracted the following from OpenSearch source code for those seeking an in-depth context :
if (ratio < 0 || ratio > 1.0) {
throw new OpenSearchParseException("Ratio should be in [0-1.0]; got [{}]"; ratio);
}
return new RatioValue(100.0 * Math.abs(ratio));
} catch (NumberFormatException e) {
throw new OpenSearchParseException("Invalid ratio or percentage [{}]"; sValue);
} }
}
}
