Invalid date received; – Elasticsearch Error How To Solve Related Issues

Invalid date received; – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

This guide will help you check for common problems that cause the error message”Invalid date received;”. To understand what might cause it to appear, read bellow frequent issues related to the Elasticsearch concepts: parser, plugin.

Advanced users might want to skip right to trying out the Elasticsearch Error Check-Up, which analyses ES to discover the cause of many errors to provide actionable recommendations (JSON based, no fee and just 2 minutes to complete).

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) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 ElasticSearch – invalid date-time format in mapping -views 1,351 ,score 1

ES Error on logstash syslog input – Invalid date format – Elasticsearch  



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now