Waiting to stop ILM because index with policy is currently in step – 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 ” Waiting to stop ILM because index with policy is currently in step ” 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 “Waiting to stop ILM because index [{}] with policy [{}] is currently in step [{}]” classname is IndexLifecycleService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     final LifecycleExecutionState lifecycleState = LifecycleExecutionState.fromIndexMetadata(idxMeta);
                    StepKey stepKey = IndexLifecycleRunner.getCurrentStepKey(lifecycleState);

                    if (OperationMode.STOPPING == currentMode) {
                        if (stepKey != null && IGNORE_STEPS_MAINTENANCE_REQUESTED.contains(stepKey.getName())) {
                            logger.info("waiting to stop ILM because index [{}] with policy [{}] is currently in step [{}]";
                                idxMeta.getIndex().getName(); policyName; stepKey.getName());
                            lifecycleRunner.maybeRunAsyncAction(clusterState; idxMeta; policyName; stepKey);
                            // ILM is trying to stop; but this index is in a Shrink step (or other dangerous step) so we can't stop
                            safeToStop = false;
                        } else {




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content