Invalid time value for field – – 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 time value for field – ” 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 time value for field [{}] – [{}]”classname  is YearTimes.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (TIME_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token != XContentParser.Token.START_ARRAY) {
 try {
 timesSet.add(DayTimes.parse(parser; token));
 } catch (ElasticsearchParseException pe) {
 throw new ElasticsearchParseException("invalid time value for field [{}] - [{}]"; pe; currentFieldName; token);
 }
 } else {
 while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
 try {
 timesSet.add(DayTimes.parse(parser; token));

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content