About to move write alias from index to index – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-8.9

Briefly, this error occurs when Elasticsearch is about to transfer the write alias from one index to another. This is a normal operation during index rollover, where the current index becomes read-only and a new index takes over write operations. However, if not handled properly, it can lead to data loss or inconsistency. To resolve this, ensure that your application can handle this switch without losing data. Also, monitor your Elasticsearch cluster to ensure that the rollover happens smoothly and the new index is properly allocated and replicated.

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

Log Context

Log “About to move write alias [{}] from index [{}] to index [{}]” classname is MlIndexAndAlias.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        String alias;
        @Nullable String currentIndex;
        String newIndex;
        ActionListener listener
    ) {
        logger.info("About to move write alias [{}] from index [{}] to index [{}]"; alias; currentIndex; newIndex);
        IndicesAliasesRequestBuilder requestBuilder = client.admin()
        if (currentIndex != null) {


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?