Warming has been interrupted – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when the warming process in Elasticsearch is interrupted. Warming is a process where data is pre-loaded into the cache to speed up queries. Interruptions can be due to system issues, insufficient resources, or abrupt shutdowns. To resolve this, ensure your system has enough resources (CPU, memory, disk space) to handle the warming process. Also, check for any system instability or network issues that could be causing interruptions. Lastly, ensure a proper shutdown process to avoid abrupt interruptions.

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.

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;


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?