No cluster-manager known for action for shard entry – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 2-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch cannot find a cluster manager for a specific action related to a shard entry. This could be due to a misconfiguration or a problem with the cluster’s state. To resolve this issue, you can try restarting the OpenSearch nodes to refresh the cluster state. If the problem persists, check your cluster settings and ensure that they are correctly configured. Additionally, you may need to check the health of your shards and consider reallocating them if necessary.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” no cluster-manager known for action [{}] for shard entry [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: cluster, shard.

Log Context

Log “no cluster-manager known for action [{}] for shard entry [{}]” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

    ) {
        ClusterStateObserver observer = new ClusterStateObserver(currentState; clusterService; null; logger; threadPool.getThreadContext());
        DiscoveryNode clusterManagerNode = currentState.nodes().getClusterManagerNode();
        Predicate changePredicate =;
        if (clusterManagerNode == null) {
            logger.warn("no cluster-manager known for action [{}] for shard entry [{}]"; actionName; request);
            waitForNewClusterManagerAndRetry(actionName; observer; request; listener; changePredicate);
        } else {
            logger.debug("sending [{}] to [{}] for shard entry [{}]"; actionName; clusterManagerNode.getId(); request);
            transportService.sendRequest(clusterManagerNode; actionName; request; new EmptyTransportResponseHandler(ThreadPool.Names.SAME) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch