Invalid date received; – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Invalid date received; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser and plugin.

Log Context

Log “Invalid date received; {}”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

Source source = source(ctx);
 // parse yyyy-MM-dd (time optional but is set to 00:00:00.000 because of the conversion to DATE
 try {
 return new Literal(source; asDateOnly(string); SqlDataTypes.DATE);
 } catch(DateTimeParseException ex) {
 throw new ParsingException(source; "Invalid date received; {}"; ex.getMessage());
 public Literal visitTimeEscapedLiteral(TimeEscapedLiteralContext ctx) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content