Refreshing cluster info – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.1-7.11

Briefly, this error occurs when Elasticsearch is trying to update its internal state about the cluster. This could be due to changes in the cluster such as adding or removing nodes, or changes in the index such as creating, deleting, or updating. To resolve this issue, ensure that all nodes in the cluster are running and network connectivity is stable. If the problem persists, consider increasing the cluster info refresh interval or disabling automatic refresh. Also, check for any heavy indexing or search operations that might be causing high load on the cluster.

This guide will help you check for common problems that cause the log ” refreshing cluster info ” 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” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     * Refreshes the ClusterInfo in a blocking fashion
    public final ClusterInfo refresh() {
        logger.trace("refreshing cluster info");
        final CountDownLatch nodeLatch = updateNodeStats(new ActionListener() {
            public void onResponse(NodesStatsResponse nodesStatsResponse) {
                ImmutableOpenMap.Builder leastAvailableUsagesBuilder = ImmutableOpenMap.builder();
                ImmutableOpenMap.Builder mostAvailableUsagesBuilder = ImmutableOpenMap.builder();


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?