Refreshed the DiscoveryNode version for node from to – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.1

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 there is a change in the version of a node in the OpenSearch cluster. The system automatically updates the DiscoveryNode version when it detects a version change. This is not necessarily an error, but more of an informational message. However, if this is causing issues, you can resolve it by ensuring all nodes in the cluster are running the same OpenSearch version. If a node was unintentionally upgraded, you may need to downgrade it to match the cluster’s version. Alternatively, plan a cluster-wide upgrade if necessary.

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 ” Refreshed the DiscoveryNode version for node {}:{} from {} to {} ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: version, cluster, node, discovery.

Log Context

Log “Refreshed the DiscoveryNode version for node {}:{} from {} to {}” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                        DiscoveryNode tmpNode = nodesBuilder.get(node.getId());
                        nodesBuilder.add(new DiscoveryNode(tmpNode.getName(); tmpNode.getId(); tmpNode.getEphemeralId();
                            tmpNode.getHostName(); tmpNode.getHostAddress(); tmpNode.getAddress(); tmpNode.getAttributes();
                            tmpNode.getRoles(); channelVersions.get(tmpNode.getId())));
              "Refreshed the DiscoveryNode version for node {}:{} from {} to {}";
                            node.getId(); node.getAddress(); node.getVersion(); channelVersions.get(tmpNode.getId()));
                } else {
                    // in case existing OpenSearch node is present in the cluster and but there is no connection to that node yet;
                    // either that node will send new JoinRequest to the master with version >=1.0; then no issue or


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