The action.autocreateindex setting is configured to be restrictive . – How to solve related issues

The action.autocreateindex setting is configured to be restrictive . – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” The action.autocreateindex setting is configured to be restrictive . ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “The [action.auto_create_index] setting is configured to be restrictive [{}].” classname is Watcher.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             }
            if (!matched) {
                throw new IllegalArgumentException(errorMessage);
            }
        }
        logger.warn("the [action.auto_create_index] setting is configured to be restrictive [{}]. " +
                " for the next 6 months daily history indices are allowed to be created; but please make sure" +
                " that any future history indices after 6 months with the pattern " +
                "[.watcher-history-YYYY.MM.dd] are allowed to be created"; value);
    }





 

Run the Check-Up to get a customized report like this:

Analyze your cluster