Prewarming worker has been interrupted – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-8.2

Briefly, this error occurs when the Elasticsearch prewarming process is interrupted. Prewarming is a process that loads frequently accessed data into cache to improve search performance. Interruptions could be due to system issues, resource constraints, or abrupt shutdowns. To resolve this, you can try restarting Elasticsearch, ensuring there are sufficient system resources, or checking for any underlying system issues that may be causing the interruption. If the problem persists, consider reviewing your prewarming settings or disabling prewarming if it’s not necessary for your use case.

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

Log Context

Log “{} prewarming worker has been interrupted” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            executor.execute(; () -> prewarmNext(executor; queue)); next.v2()));
        } catch (InterruptedException e) {
            logger.warn(() -> new ParameterizedMessage("{} prewarming worker has been interrupted"; shardId); e);

    public static Directory create(
        RepositoriesService repositories;


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?