Expected; but did not find; a dynamic hosts list at – How to solve related issues

Opster Team

Dec-19, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

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: discovery-azure-classic, discovery-file and hosts.

Log Context

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

             deprecationLogger.deprecated("Found dynamic hosts list at [{}] but this path is deprecated. This list should be at [{}] " +
                "instead. Support for the deprecated path will be removed in future."; legacyUnicastHostsFilePath; unicastHostsFilePath);
            return readFileContents(legacyUnicastHostsFilePath);

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

        return Collections.emptyList();

    private List readFileContents(Path path) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content