Cannot parse duration – Elasticsearch Error How To Solve Related Issues

Cannot parse duration – 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 “Cannot parse duration” 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: plugin.

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”Cannot parse duration [{}]”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

case SECOND:
  return Duration.ZERO.plusSeconds(duration);
  return Duration.ZERO.plusMillis(duration);
  throw new ParsingException(source; "Cannot parse duration [{}]"; unit);
  } catch (ArithmeticException ae) {
  throw new ParsingException(source; "Value [{}] cannot be used as it is too large to convert into [{}]s"; duration; unit);

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 cannot parse date using custom format -views 4,349 ,score 1

Elasticsearch 2.2 : Cannot parse dates -views   1,206,score 3

Find Configuration Errors

Analyze Now