Could not parse schedule. could not parse as a duration – Elasticsearch Error How To Solve Related Issues

Could not parse schedule. could not parse as a 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 “could not parse schedule. could not parse as a 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”could not parse [{}] schedule. could not parse [{}] as a [{}] duration”classname  is IntervalSchedule.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

assert value.endsWith(suffix);
  String num = value.substring(0; value.indexOf(suffix));
  try {
  return Long.parseLong(num);
  } catch (NumberFormatException nfe) {
  throw new ElasticsearchParseException("could not parse [{}] schedule. could not parse [{}] as a [{}] duration";
  TYPE; num; name().toLowerCase(Locale.ROOT));
  }
  }
 
  public String format(long duration) {

 

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 watcher could not parse search input -views 1,296 ,score 1

How do I create a cron expression running in Kibana on weekday? -views   793

 

 

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now