Index was already rolled over for alias . not attempting to roll over again – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when an index was already rolled over for a specific alias, and Elasticsearch is not attempting to roll over again. This can happen when there is a misconfiguration of the rollover process or when there is an issue with the index. To resolve this issue, you can try to check the rollover process and the index for errors, or try to roll over the index again.

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 ” 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 and 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 :

                 indexMetaData.getIndex().getName())));
            return;
        }

        if (indexMetaData.getRolloverInfos().get(rolloverAlias) != null) {
            logger.info("index [{}] was already rolled over for alias [{}]; not attempting to roll over again";
                indexMetaData.getIndex().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?

Analyze your cluster & get personalized recommendations

Skip to content