Timed out getting cluster state – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.11-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve the cluster state within the specified timeout period. This could be due to network issues, heavy load on the cluster, or a misconfiguration. To resolve this issue, you can increase the timeout setting, ensure the cluster is not overloaded by optimizing queries or adding more nodes, and check the network connectivity between nodes. Also, verify your cluster settings and configurations to ensure they are correct.

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

Log Context

Log “Timed out getting cluster state” class name is RestClusterStateAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public Iterator toXContentChunked(ToXContent.Params outerParams) {
 if (request.local() == false
 && currentTimeMillisSupplier.getAsLong() - startTimeMillis > request.masterNodeTimeout().millis()) {
 throw new ElasticsearchTimeoutException("Timed out getting cluster state");
 }  final ClusterState responseState = response.getState();  return Iterators.concat(Iterators.single((builder; params) -> {


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?