Log Current step for index with policy is not recognized – How To Solve Related Issues



Log 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 read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Current step for index with policy is not recognized ” 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: index and plugin.

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. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

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 {}";






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 Github Issue Number 33074

2 Ilm Policy Is Not Working






Optimize Elasticsearch Performance

Try The Tool