How To Solve Issues Related to Log – Waiting to stop ILM because index with policy is currently in step

How To Solve Issues Related to Log – Waiting to stop ILM because index with policy is currently in step

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Waiting to stop ILM because index with policy is currently in step” it’s important to understand a few problems related to Elasticsearch concepts index, plugin. See bellow important tips and explanations on these concepts

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 {




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 Ilm Waiting For Allocation  

Github Issue Number 46357  

Github Issue Number 34648

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now