failed to perform on node – How To Solve Related Issues

failed to perform on node – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” failed to perform on node ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: node and replication.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

                     
Override
                    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);
                        }
                    }
                }
            );



 

Optimize Elasticsearch Performance

Try The Tool