Refreshing cluster info in background – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch is trying to update the cluster information in the background. This is a routine process and not necessarily an error, but it could indicate a problem if it’s happening too frequently or causing performance issues. To resolve this, you could check the cluster health and ensure it’s stable. If the cluster is unstable, you might need to adjust the cluster settings or add more nodes. Additionally, ensure that your network connection is stable and that there are no issues with the underlying hardware.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

Log Context

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


    private void executeRefresh(ClusterState clusterState; String reason) {
        if (clusterState.nodes().getDataNodes().size() > 1) {
            logger.trace("refreshing cluster info in background [{}]"; reason);
            threadPool.executor(REFRESH_EXECUTOR).execute(new RefreshRunnable(reason));



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?

Get expert answers on Elasticsearch/OpenSearch