Moving index from to in policy – How to solve related issues

Average Read Time

2 Mins

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Moving index from to in policy ” 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 (free tool that requires no installation).

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);


Run the Check-Up to get a customized report like this:

Analyze your cluster