Top warming has been interrupted – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.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 OpenSearch operation.

Briefly, this error occurs when the process of warming up the cache for the top queries in OpenSearch is interrupted. This could be due to a sudden shutdown, memory issues, or other system interruptions. To resolve this, you can try restarting the OpenSearch service, ensuring there’s enough memory for the operation, or checking for any system issues that might be causing the interruption. If the problem persists, consider reviewing your cache settings or the complexity of your top queries.

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 ” top warming has been interrupted ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: index.

Log Context

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

        for (TerminationHandle terminationHandle : terminationHandles) {
            try {
            } catch (InterruptedException e) {
                logger.warn("top 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?

Get expert answers on Elasticsearch/OpenSearch