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

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

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “Invalid time received;” 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: parser, 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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

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

// parse HH:mm:ss
  try {
  return new Literal(source; asTimeOnly(string); SqlDataTypes.TIME);
  } catch (DateTimeParseException ex) {
  throw new ParsingException(source; "Invalid time received; {}"; ex.getMessage());
  public Literal visitTimestampEscapedLiteral(TimestampEscapedLiteralContext 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

Curator: “Invalid epoch received, unable to convert None to int …  



About Opster

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

Find Configuration Errors

Analyze Now