Refreshing cluster info rejected – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.1-7.11

Briefly, this error occurs when Elasticsearch is unable to update its internal state about the cluster’s nodes due to high load or resource constraints. This could be due to a large number of requests, insufficient memory, or network issues. To resolve this, you can try reducing the load on the cluster by limiting the number of concurrent requests, increasing the memory allocation, or improving the network connectivity. Additionally, ensure that the cluster state is not excessively large by limiting the number of indices and shards.

This guide will help you check for common problems that cause the log ” refreshing cluster info rejected [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “refreshing cluster info rejected [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        public void onRejection(Exception e) {
            final boolean shutDown = e instanceof EsRejectedExecutionException && ((EsRejectedExecutionException) e).isExecutorShutdown();
            logger.log(shutDown ? Level.DEBUG : Level.WARN; "refreshing cluster info rejected [{}]"; reason; 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?