Moving index from to in policy – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is trying to move an index from one phase to another in an Index Lifecycle Management (ILM) policy, but encounters an issue. This could be due to a misconfiguration in the ILM policy, insufficient resources, or a network issue. To resolve this, you can check the ILM policy configuration for any errors, ensure there are enough resources (like disk space) for the operation, and verify network connectivity. If the issue persists, you may need to manually move the index or temporarily disable the ILM policy.

This guide will help you check for common problems that cause the log ” moving index [{}] from [{}] to [{}] in policy [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “moving index [{}] from [{}] to [{}] in policy [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        IndexMetadata idxMeta = state.getMetadata().index(index);
        Step.StepKey currentStepKey = Step.getCurrentStepKey(idxMeta.getLifecycleExecutionState());
        validateTransition(idxMeta; currentStepKey; newStepKey; stepRegistry);

        String policyName = idxMeta.getLifecyclePolicyName();"moving index [{}] from [{}] to [{}] in policy [{}]"; index.getName(); currentStepKey; newStepKey; policyName);

        IndexLifecycleMetadata ilmMeta = state.metadata().custom(IndexLifecycleMetadata.TYPE);
        LifecyclePolicyMetadata policyMetadata = ilmMeta.getPolicyMetadatas().get(idxMeta.getLifecyclePolicyName());
        LifecycleExecutionState lifecycleState = idxMeta.getLifecycleExecutionState();
        LifecycleExecutionState newLifecycleState = updateExecutionStateToStep(


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?