Failed to perform on node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to execute a specific operation on a node due to issues like insufficient resources, network connectivity problems, or configuration errors. To resolve this, you can check the node’s logs for more detailed error information. Ensure the node has enough resources (CPU, memory, disk space). Verify the network connectivity between the nodes. Lastly, check the Elasticsearch configuration for any inconsistencies or errors.

This guide will help you check for common problems that cause the log ” {} failed to perform {} on node {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and replication.

Log Context

Log “{} failed to perform {} on node {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    public void handleException(TransportException exp) {
                        onReplicaFailure(nodeId; exp);
                        logger.trace("[{}] transport failure during replica request [{}]; action [{}]"; exp; node; replicaRequest; transportReplicaAction);
                        if (ignoreReplicaException(exp) == false) {
                            logger.warn("{} failed to perform {} on node {}"; exp; shardId; transportReplicaAction; node);
                            shardStateAction.shardFailed(shard; indexUUID; "failed to perform " + actionName + " on replica on node " + node; exp);


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?