Updating action.operate-all-indices from to – How To Solve Related Issues

Updating action.operate-all-indices from to – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0


Before you begin reading this guide, we recommend you try running the 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 ” Updating action.operate-all-indices from to ” 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: index.

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 “updating [action.operate_all_indices] from [{}] to [{}]” classname is DestructiveOperations.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    public void onRefreshSettings(Settings settings) {
        boolean newValue = settings.getAsBoolean(DestructiveOperations.REQUIRES_NAME; destructiveRequiresName);
        if (destructiveRequiresName != newValue) {
            logger.info("updating [action.operate_all_indices] from [{}] to [{}]"; destructiveRequiresName; newValue);
            this.destructiveRequiresName = newValue;

    private static boolean hasWildcardUsage(String aliasOrIndex) {


Optimize Elasticsearch Performance

Try The Tool