Source has ” + response.getFailedShards() + ” failed shards – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

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

This guide will help you check for common problems that cause the log ” Source has ” + response.getFailedShards() + ” failed shards ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: response, source and plugin.

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 “Source has [” + response.getFailedShards() + “] failed shards”classname  is DefaultCheckpointProvider.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

ClientHelper.TRANSFORM_ORIGIN;
 IndicesStatsAction.INSTANCE;
 new IndicesStatsRequest().indices(indices).clear().indicesOptions(IndicesOptions.LENIENT_EXPAND_OPEN);
 ActionListener.wrap(response -> {
 if (response.getFailedShards() != 0) {
 listener.onFailure(new CheckpointException("Source has [" + response.getFailedShards() + "] failed shards"));
 return;
 }
 listener.onResponse(extractIndexCheckPoints(response.getShards(); userIndices; prefix));
 }; e -> listener.onFailure(new CheckpointException("Failed to create checkpoint"; e)))
 );

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content