Not adding address is null host type – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 2.9-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 tries to add a node to the cluster but the address of the node is null. This could be due to incorrect configuration or network issues. To resolve this, ensure that the node’s network settings are correctly configured, including the hostname and IP address. Also, check if the node is reachable over the network. If the problem persists, review the OpenSearch logs for more detailed information about the error.

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 ” not adding {}; address is null; host_type {} ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: discovery, plugins, discovery-ec2.

Log Context

Log “not adding {}; address is null; host_type {}” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                } else {
                    logger.warn("not adding {}; address is null; host_type {}"; instance.instanceId(); hostType);
        }"using dynamic transport addresses {}"; dynamicHosts);


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