Percent value – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

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 encounters a percentage value that it cannot process correctly. This could be due to incorrect formatting, a value outside the acceptable range, or a conflict with the field mapping. To resolve this issue, you can check the format of the percentage value to ensure it’s correct. If the format is correct, verify that the value is within the acceptable range. Lastly, check the field mapping to ensure it’s compatible with percentage values. If necessary, you may need to update the field mapping.

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 ” Percent [{}]; value [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations.

Log Context

Log “Percent [{}]; value [{}]” classname is percentile-aggregation.asciidoc.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // For each entry
for (Percentile entry : agg) {
    double percent = entry.getPercent();    // Percent
    double value = entry.getValue();        // Value

    logger.info("percent [{}]; value [{}]"; percent; value);
}
--------------------------------------------------


This will basically produce for the first example:




 

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?

Get expert answers on Elasticsearch/OpenSearch