Rejecting request since local state is – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when Elasticsearch rejects a request because the local state of the node is not in sync with the cluster state. This could be due to network issues, heavy load, or a slow node. To resolve this, you can try restarting the node, increasing the node’s resources, or optimizing your queries to reduce load. Also, ensure your network connectivity is stable. If the problem persists, consider adding more nodes to your cluster to distribute the load and improve performance.

This guide will help you check for common problems that cause the log ” rejecting ” + request + ” since local state is ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request, cluster.

Log Context

Log “rejecting ” + request + ” since local state is ” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  if (request.term < responder.term) {
 throw new CoordinationStateRejectedException("rejecting " + request + " since local state is " + this);
 }  transportService.getThreadPool()
 .execute(; new CheckedSupplier<>() {


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?