Failed to parse as a double – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch attempts to parse a value as a double data type, but the value is not compatible. This could be due to incorrect data type in the mapping or a non-numeric value being indexed in a double field. To resolve this, ensure that the data type in your mapping matches the data you’re indexing. If the data type is correct, check the data being indexed for any non-numeric values. If necessary, you may need to clean or transform your data before indexing it.

This guide will help you check for common problems that cause the log ” failed to parse [{}] as a double ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “failed to parse [{}] as a double” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 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);
 } else {
 return parseBytesSizeValue(sValue; settingName);


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?