Opster Team
Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
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. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Updating action.operate-all-indices from to ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

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 :
Override 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) {
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 2 minutes
Arpit Ghiya
Senior Lead SRE at Coupa