Starting to track leader shard – 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 ” Starting to track leader shard ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin 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 “{} Starting to track leader shard {}” classname is ShardFollowTasksExecutor.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
    
Override
    protected void nodeOperation(final AllocatedPersistentTask task; final ShardFollowTask params; final PersistentTaskState state) {
        Client followerClient = wrapClient(client; params.getHeaders());
        ShardFollowNodeTask shardFollowNodeTask = (ShardFollowNodeTask) task;
        logger.info("{} Starting to track leader shard {}"; params.getFollowShardId(); params.getLeaderShardId());

        FollowerStatsInfoHandler handler = (followerHistoryUUID; followerGCP; maxSeqNo) -> {
            shardFollowNodeTask.start(followerHistoryUUID; followerGCP; maxSeqNo; followerGCP; maxSeqNo);
        };
        Consumer errorHandler = e -> {



 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content