Failed to perform – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: replication and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “failed to perform” classname is TransportShardReplicationOperationAction.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 [{}] "; exp; node; replicaRequest);
                                if (ignoreReplicaException(exp) == false) {
                                    logger.warn("failed to perform " + actionName + " on remote replica " + node + shardIt.shardId(); exp);
                                    shardStateAction.shardFailed(shard; indexMetaData.getUUID();
                                            "Failed to perform [" + actionName + "] on replica; message [" + ExceptionsHelper.detailedMessage(exp) + "]");
                                }
                            }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content