Timeout waiting for ; request: – 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 Check-Up which can resolve issues that cause many errors.

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

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 “Timeout waiting for [{}]; request: {}”classname  is TransportInstanceSingleOperationAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (observer.isTimedOut()) {
 // we running as a last attempt after a timeout has happened. don't retry
 Exception listenFailure = failure;
 if (listenFailure == null) {
 if (shardIt == null) {
 listenFailure = new UnavailableShardsException(request.concreteIndex(); -1; "Timeout waiting for [{}]; request: {}";
 request.timeout(); actionName);
 } else {
 listenFailure = new UnavailableShardsException(shardIt.shardId();
 "[{}] shardIt; [{}] active : Timeout waiting for [{}]; request: {}"; shardIt.size(); shardIt.sizeActive();
 request.timeout(); actionName);


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content