Failed to send shard started to – 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 send shard started to ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster 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 send shard started to [{}]” classname is ShardStateAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         logger.debug("{} sending shard started for {}"; shardRoutingEntry.shardRouting.shardId(); shardRoutingEntry);
        transportService.sendRequest(masterNode;
                SHARD_STARTED_ACTION_NAME; new ShardRoutingEntry(shardRouting; indexUUID; reason; null); new EmptyTransportResponseHandler(ThreadPool.Names.SAME) {
                    
Override
                    public void handleException(TransportException exp) {
                        logger.warn("failed to send shard started to [{}]"; exp; masterNode);
                    }

                });
    }




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content