Index was already rolled over for alias not attempting to roll over again – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-7.15

Briefly, this error occurs when an attempt is made to roll over an Elasticsearch index that has already been rolled over. This is a protective measure to prevent data loss or corruption. To resolve this issue, you can either create a new index and attempt the rollover again, or check the alias settings to ensure it’s pointing to the correct index. Additionally, ensure that your rollover conditions (like max_age, max_docs, or max_size) are properly set to avoid unnecessary rollovers.

This guide will help you check for common problems that cause the log ” index [{}] was already rolled over for alias [{}]; not attempting to roll over again ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: alias, index, plugin.

Log Context

Log “index [{}] was already rolled over for alias [{}]; not attempting to roll over again” classname is WaitForRolloverReadyStep.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    index.getName())));
                return;
            }

            if (indexMetadata.getRolloverInfos().get(rolloverAlias) != null) {
                logger.info("index [{}] was already rolled over for alias [{}]; not attempting to roll over again";
                    index.getName(); rolloverAlias);
                listener.onResponse(true; new WaitForRolloverReadyStep.EmptyInfo());
                return;
            }

 

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?