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

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when an Elasticsearch operation is attempted on a configuration that is in the process of migration. This could be due to a cluster update, index settings change, or other configuration modifications. To resolve this issue, you can wait for the migration process to complete before retrying the operation. Alternatively, you can check the cluster health or migration status to ensure all nodes are functioning properly and the migration process has successfully completed. If the error persists, consider reviewing your migration strategy to avoid conflicts.

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” class name 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


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?