Timed out after – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when a request to Elasticsearch exceeds the set timeout period. This could be due to heavy load, insufficient resources, or network issues. To resolve this, you can increase the timeout limit, optimize your queries for better performance, or scale your Elasticsearch cluster to handle more load. Additionally, check your network for any issues that might be causing delays.

This guide will help you check for common problems that cause the log ” Timed out after [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Timed out after [” class name is TransportStopRollupAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (stopped) {
 // We have successfully confirmed a stop; send back the response
 } else {
 listener.onFailure(new ElasticsearchTimeoutException("Timed out after [" + request.timeout().getStringRep()
 + "] while waiting for rollup job [" + request.getId() + "] to stop. State was ["
 + ((RollupJobStatus) jobTask.getStatus()).getIndexerState() + "]"));
 } catch (InterruptedException e) {


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?