Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.
Briefly, this error occurs when an invalid hour value is inputted into Elasticsearch. The hour value should be between 0 and 23 (inclusive), representing the 24 hours in a day. If a value outside this range is entered, Elasticsearch will throw this error. To resolve this issue, ensure that the hour value you’re inputting is within the acceptable range. If you’re using a script or automated process to input data, check that it’s correctly formatted to avoid generating invalid hour values.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “invalid time hour value [{}] (possible values may be between 0 and 23 incl.)” class name 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) == false) {
throw new ElasticsearchParseException("invalid time hour value [{}] (possible values may be between 0 and 23 incl.)";
hour);
}
return hour; case VALUE_STRING:
