Unknown date time unit id id – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

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 Elasticsearch encounters an unrecognized date time unit in a query or script. This could be due to a typo or using a unit that is not supported. To resolve this issue, you should first check the date time unit you’re using for any spelling mistakes. If there are none, ensure that the unit is one that Elasticsearch supports. For example, Elasticsearch recognizes units like “d” for days, “h” for hours, “m” for minutes, etc. Adjust your query or script accordingly to use a recognized date time unit.

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 ” Unknown date time unit id [” + id + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “Unknown date time unit id [” + id + “]” class name is Rounding.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 case 4 -> MONTH_OF_YEAR;
 case 5 -> DAY_OF_MONTH;
 case 6 -> HOUR_OF_DAY;
 case 7 -> MINUTES_OF_HOUR;
 case 8 -> SECOND_OF_MINUTE;
 default -> throw new ElasticsearchException("Unknown date time unit id [" + id + "]");
 };
 }
 }  public abstract void innerWriteTo(StreamOutput out) throws IOException;

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?