How To Solve Issues Related to Log – Failed to update seed list for cluster:

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Prevent Issue

Updated: Jan-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Failed to update seed list for cluster:” it’s important to understand common problems related to Elasticsearch concepts: cluster. See detailed explanations below complete with common problems, examples and useful tips.

Cluster in Elasticsearch

What is it

In Elasticsearch a cluster is a collection of one or more nodes (servers / VMs). A cluster can consist of an unlimited number of nodes. The cluster provides interface for indexing and storing data and search capability across all of the data which is stored in the data nodes

Each cluster has a single master node that is elected by the master eligible nodes. In cases where the master is not available the other connected master eligible nodes elect a new master. Clusters are identified by a unique name, which defaults to “Elasticsearch”.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Github Issue Number 26961  

2Cross Cluster Search Comprehension  


Log Context

Log ”Failed to update seed list for cluster:” classname is RemoteClusterService.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

                         exception -> {
                            if (countDown.fastForward()) {
                                connectionListener.onFailure(exception);
                            }
                            if (finalRemote.isClosed() == false) {
                                logger.warn("failed to update seed list for cluster: " + clusterAlias; exception);
                            }
                        }));
            }
        }
        this.remoteClusters = Collections.unmodifiableMap(remoteClusters);






About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster