Faulty node – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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.

This guide will help you check for common problems that cause the log ” faulty node ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, node.

Log Context

Log “faulty node”classname  is Publication.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 void onFaultyNode(DiscoveryNode faultyNode) {
 if (isActive() && discoveryNode.equals(faultyNode)) {
 logger.debug("onFaultyNode: [{}] is faulty; failing target in publication {}"; faultyNode; Publication.this);
 setFailed(new ElasticsearchException("faulty node"));
 DiscoveryNode getDiscoveryNode() {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content