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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” cant send shard started for ; no master known. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and shard.

Log Context

Log “{} can’t send shard started for {}; no master known.” classname is
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);
        shardStarted(shardRouting; indexUUID; reason; masterNode);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content