Cannot as the configuration is temporarily pending migration – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” cannot as the configuration is temporarily pending migration ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “cannot {} as the configuration [{}] is temporarily pending migration”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static ElasticsearchStatusException badRequestException(String msg; Object... args) {
 return new ElasticsearchStatusException(msg; RestStatus.BAD_REQUEST; args);
 public static ElasticsearchStatusException configHasNotBeenMigrated(String verb; String id) {
 return new ElasticsearchStatusException("cannot {} as the configuration [{}] is temporarily pending migration";
 RestStatus.SERVICE_UNAVAILABLE; verb; id);
 * Creates an error message that explains there are shard failures; displays info


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content