Time exceeded – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Time exceeded ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, query.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Time exceeded”classname  is QueryPhase.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } catch (TimeExceededException e) {
 assert timeoutSet : "TimeExceededException thrown even though timeout wasn't set";
 if (searchContext.request().allowPartialSearchResults() == false) {
 // Can't rethrow TimeExceededException because not serializable
 throw new QueryPhaseExecutionException(searchContext.shardTarget(); "Time exceeded");
 if (searchContext.terminateAfter() != SearchContext.DEFAULT_TERMINATE_AFTER && queryResult.terminatedEarly() == null) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content