Log No master known for action for shard entry – How To Solve Related Issues



Log 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 try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “No master known for action for shard entry” 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, master, 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 discover the cause of many errors and provides suitable actionable recommendations. 

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) {




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Elasticsearch Cluster – No known master node, scheduling a retry -views 17.80 K ,score 8

Github Issue Number 23199  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now