Marking node as faulty – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 2-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 detects that a node in the cluster is not functioning correctly. This could be due to network issues, hardware failure, or the node running out of resources. To resolve this issue, you can try restarting the faulty node, checking its network connectivity, ensuring it has sufficient resources (like memory and disk space), or replacing the faulty hardware. If the node is consistently marked as faulty, it might be beneficial to remove it from the cluster and add a new, healthy node.

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 ” {} marking node as faulty ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: cluster, node.

Log Context

Log “{} marking node as faulty” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                    synchronized (mutex) {
                        if (running() == false) {
                            logger.trace("{} no longer running; not marking faulty"; FollowerChecker.this);
              "{} marking node as faulty"; FollowerChecker.this);
                    onNodeFailure.accept(discoveryNode; reason);


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