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 the percentage value provided in an Elasticsearch operation exceeds the valid range of 0-100. This could be due to a programming error or incorrect user input. To resolve this issue, you should validate the percentage input before using it in Elasticsearch operations. Ensure that the percentage value is within the acceptable range. If the error persists, check the code for any miscalculations or misinterpretations of the percentage 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 ” percentage should be in [0-100]; got [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “percentage should be in [0-100]; got [{}]” class name is MemorySizeValue.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (sValue != null && sValue.endsWith("%")) {
final String percentAsString = sValue.substring(0; sValue.length() - 1);
try {
final double percent = Double.parseDouble(percentAsString);
if (percent < 0 || percent > 100) {
throw new ElasticsearchParseException("percentage should be in [0-100]; got [{}]"; percentAsString);
}
return ByteSizeValue.ofBytes((long) ((percent / 100) * JvmInfo.jvmInfo().getMem().getHeapMax().getBytes()));
} catch (NumberFormatException e) {
throw new ElasticsearchParseException("failed to parse [{}] as a double"; e; percentAsString);
}
