Current step for index with policy is not recognized – 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 ” Current step for index with policy is not recognized ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and plugin.

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 “Current step [{}] for index [{}] with policy [{}] is not recognized” classname is IndexLifecycleRunner.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     public void maybeRunAsyncAction(ClusterState currentState; IndexMetaData indexMetaData; String policy; StepKey expectedStepKey) {
        String index = indexMetaData.getIndex().getName();
        LifecycleExecutionState lifecycleState = LifecycleExecutionState.fromIndexMetadata(indexMetaData);
        Step currentStep = getCurrentStep(stepRegistry; policy; indexMetaData; lifecycleState);
        if (currentStep == null) {
            logger.warn("current step [{}] for index [{}] with policy [{}] is not recognized";
                getCurrentStepKey(lifecycleState); index; policy);
            return;
        }

        logger.trace("[{}] maybe running async action step ({}) with current step {}";




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content