No master known for action for shard entry – 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 ” No master known for action for shard entry ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, master 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 “No master known for action [{}] for shard entry [{}]” classname is ShardStateAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         ClusterStateObserver observer =
            new ClusterStateObserver(currentState; clusterService; null; logger; threadPool.getThreadContext());
        DiscoveryNode masterNode = currentState.nodes().getMasterNode();
        Predicate changePredicate = MasterNodeChangePredicate.build(currentState);
        if (masterNode == null) {
            logger.warn("no master known for action [{}] for shard entry [{}]"; actionName; request);
            waitForNewMasterAndRetry(actionName; observer; request; listener; changePredicate);
        } else {
            logger.debug("sending [{}] to [{}] for shard entry [{}]"; actionName; masterNode.getId(); request);
            transportService.sendRequest(masterNode;
                actionName; request; new EmptyTransportResponseHandler(ThreadPool.Names.SAME) {




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content