Moved from to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 5-5

Briefly, this error occurs when Elasticsearch tries to relocate a shard from one node to another, but the process fails. This could be due to insufficient disk space, network issues, or the target node being unable to accept more shards. To resolve this, you can check the disk space and network connectivity of your nodes. If they are fine, consider adjusting the cluster settings to allow more shards on the target node or add more nodes to your cluster.

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

Log Context

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

             logger.error((Supplier>) () -> new ParameterizedMessage("multiple nodes trying to upgrade [{}] in parallel; retry " +
                "upgrading with single node"; target); exception);
            throw exception;
        } finally {
            if (success) {
      "{} moved from [{}] to [{}]"; index; source; target);
                logger.trace("{} syncing directory [{}]"; index; target);
                IOUtils.fsync(target; true);


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?