Moving index from to in policy – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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: index and plugin.

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 :

         if (stepRegistry.stepExists(indexPolicySetting; nextStepKey) == false) {
            throw new IllegalArgumentException("step [" + nextStepKey + "] for index [" + idxMeta.getIndex().getName() +
                "] with policy [" + indexPolicySetting + "] does not exist");
        }"moving index [{}] from [{}] to [{}] in policy [{}]";
            indexName; currentStepKey; nextStepKey; indexPolicySetting);

        return IndexLifecycleRunner.moveClusterStateToNextStep(idxMeta.getIndex(); currentState; currentStepKey;
            nextStepKey; nowSupplier; forcePhaseDefinitionRefresh);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content