Warming has been interrupted – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Warming has been interrupted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices and warmer.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “warming has been interrupted” classname is IndicesWarmer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             } catch (InterruptedException e) {
                if (topReader) {
                    logger.warn("top warming has been interrupted"; e);
                } else {
                    logger.warn("warming has been interrupted"; e);
        long took = System.nanoTime() - time;


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content