Failed to apply started shards – How to solve related issues

Opster Team

Jan-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 apply started shards ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and shards.

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 apply started shards {}” classname is ShardStateAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             ClusterState maybeUpdatedState = currentState;
            try {
                maybeUpdatedState = allocationService.applyStartedShards(currentState; shardRoutingsToBeApplied);
                builder.successes(tasksToBeApplied);
            } catch (Exception e) {
                logger.warn(() -> new ParameterizedMessage("failed to apply started shards {}"; shardRoutingsToBeApplied); e);
                builder.failures(tasksToBeApplied; e);
            }

            return builder.build(maybeUpdatedState);
        }




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content