Invalid time hour value (possible values may be between 0 and 23 incl.) – Elasticsearch Error How To Solve Related Issues

Invalid time hour value (possible values may be between 0 and 23 incl.) – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” invalid time hour value (possible values may be between 0 and 23 incl.) ” 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”invalid time hour value [{}] (possible values may be between 0 and 23 incl.)”classname  is DayTimes.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static int parseHourValue(XContentParser parser; XContentParser.Token token) throws IOException; ElasticsearchParseException {
  switch (token) {
  case VALUE_NUMBER:
  int hour = parser.intValue();
  if (!DayTimes.validHour(hour)) {
  throw new ElasticsearchParseException("invalid time hour value [{}] (possible values may be between 0 and 23 incl.)";
  hour);
  }
  return hour;
 
  case VALUE_STRING:

 

Optimize Elasticsearch Performance

Try The Tool