Attempt to execute a cluster health operation without a task – How to solve related issues

Attempt to execute a cluster health operation without a task – 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 ” Attempt to execute a cluster health operation without a task ” 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: admin, cluster and task.

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

Log “Attempt to execute a cluster health operation without a task” classname is TransportClusterHealthAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     }

    
Override
    protected final void masterOperation(ClusterHealthRequest request; ClusterState state;
                                         ActionListener listener) throws Exception {
        logger.warn("attempt to execute a cluster health operation without a task");
        throw new UnsupportedOperationException("task parameter is required for this operation");
    }

    
Override
    protected void masterOperation(Task task; final ClusterHealthRequest request; final ClusterState unusedState;


 

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

Analyze your cluster