Could not parse schedule. unexpected token – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” could not parse schedule. unexpected token ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “could not parse [{}] schedule. unexpected token [{}]”classname  is HourlySchedule.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

XContentParser.Token token;
 while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
 if (token == XContentParser.Token.FIELD_NAME) {
 currentFieldName = parser.currentName();
 } else if (currentFieldName == null) {
 throw new ElasticsearchParseException("could not parse [{}] schedule. unexpected token [{}]"; TYPE; token);
 } else if (MINUTE_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token.isValue()) {
 try {
 minutes.add(DayTimes.parseMinuteValue(parser; token));
 } catch (ElasticsearchParseException pe) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content