Percentage should be in 0-100; got – Elasticsearch Error How To Solve Related Issues

Percentage should be in 0-100; got – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “percentage should be in 0-100; got” 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: .

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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”percentage should be in [0-100]; got [{}]”classname  is
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  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);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Elasticsearch: score in percentage, with multi_match (fuzziness enabled) and filter in the same query, based in the multi_match part only -views 698 ,score 1

How to get 100 score in elasticsearch -views   387

Find Configuration Errors

Analyze Now