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

Average Read Time

2 Mins

Failed to parse as a double – 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” failed to parse as a double ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: Node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

if (percent  100) {
  throw new ElasticsearchParseException("percentage should be in [0-100]; got [{}]"; percentAsString);
  return new ByteSizeValue((long) ((percent / 100) * JvmInfo.jvmInfo().getMem().getHeapMax().getBytes()); ByteSizeUnit.BYTES);
  } catch (NumberFormatException e) {
  throw new ElasticsearchParseException("failed to parse [{}] as a double"; e; percentAsString);
  } else {
  return parseBytesSizeValue(sValue; settingName);


Run the Check-Up to get a customized report like this:

Analyze your cluster