Using dynamic transport addresses – 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 is using dynamic transport addresses, which means it’s automatically determining the transport address. This could be due to misconfiguration or network issues. To resolve this, you can manually specify the transport address in the OpenSearch configuration file. Also, ensure that the network settings are correct and the required ports are open. If the issue persists, check the logs for more detailed error messages and troubleshoot accordingly.

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 ” using dynamic transport addresses {} ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: plugins, discovery-ec2, discovery.

Log Context

Log “using dynamic transport addresses {}” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

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

        return dynamicHosts;

    private DescribeInstancesRequest buildDescribeInstancesRequest() {


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