Reset mode has been enabled – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.13-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when the Elasticsearch cluster is set to reset mode. This mode is typically used during maintenance or troubleshooting, and it prevents any changes to the cluster’s state. To resolve this issue, you can disable the reset mode by using the appropriate API command. Alternatively, if you’re performing maintenance or troubleshooting, you may want to leave the reset mode enabled until you’re finished. Always ensure to disable it once you’re done to allow normal operations.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Reset mode has been enabled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Reset mode has been enabled” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 clusterService.addListener((event) -> {
 if (event.metadataChanged()) {
 isResetMode = MlMetadata.getMlMetadata(event.state()).isResetMode();
 if (isResetMode) {
 final RuntimeException exception = new CancellableThreads.ExecutionCancelledException("Reset mode has been enabled");
 for (RetryableAction action : onGoingRetryableBulkActions.values()) {


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?