Expected but did not find a dynamic hosts list at – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to locate a dynamic hosts list at a specified path. This could be due to incorrect configuration or the list not existing at the specified location. To resolve this, ensure that the path to the dynamic hosts list is correctly specified in the Elasticsearch configuration. Also, verify that the dynamic hosts list exists at the specified path. If not, create it. Additionally, check the file permissions to ensure Elasticsearch has the necessary access to read the file.

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 ” expected; but did not find; a dynamic hosts list at [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: hosts, discovery.

Log Context

Log “expected; but did not find; a dynamic hosts list at [{}]” classname is FileBasedSeedHostsProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                logger.warn(() -> "failed to read file [" + unicastHostsFilePath + "]"; e);
                return Collections.emptyList();
            }
        }

        logger.warn("expected; but did not find; a dynamic hosts list at [{}]"; unicastHostsFilePath);

        return Collections.emptyList();
    }

    @Override

 

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?