cant send shard started for ; no master known. – How to solve related issues

Average Read Time

2 Mins

cant send shard started for ; no master known. – 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 ” cant send shard started for ; no master known. ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

Log “{} can’t send shard started for {}; no master known.” classname is ShardStateAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     }

    public void shardStarted(final ShardRouting shardRouting; String indexUUID; final String reason) {
        DiscoveryNode masterNode = clusterService.state().nodes().masterNode();
        if (masterNode == null) {
            logger.warn("{} can't send shard started for {}; no master known."; shardRouting.shardId(); shardRouting);
            return;
        }
        shardStarted(shardRouting; indexUUID; reason; masterNode);
    }





 

Run the Check-Up to get a customized report like this:

Analyze your cluster