Invalid month day value. expected a string or a number value; but found – 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 ” invalid month day value. expected a string or a number value; but found ” 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 “invalid month day value. expected a string or a number value; but found [{}]”classname  is MonthTimes.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 }
 if (token == XContentParser.Token.VALUE_NUMBER) {
 return parser.intValue();
 }
 throw new ElasticsearchParseException("invalid month day value. expected a string or a number value; but found [{}]"; token);
 } 
 public static class Builder { 
 private final Set days = new HashSet<>();

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content