Interrupted while waiting for scheduler engine termination – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is interrupted while waiting for the termination of a scheduled task. This could be due to a slow or unresponsive task, or a sudden shutdown of the Elasticsearch service. To resolve this issue, you can try to identify and optimize slow tasks, ensure that the Elasticsearch service is not being abruptly stopped, or increase the timeout settings if the tasks are expected to take a long time. Additionally, ensure that your system has sufficient resources to handle the tasks.

This guide will help you check for common problems that cause the log ” interrupted while waiting for scheduler engine termination ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “interrupted while waiting for scheduler engine termination” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            final boolean terminated = scheduler.awaitTermination(5L; TimeUnit.SECONDS);
            if (terminated == false) {
                logger.warn("scheduler engine was not terminated after waiting 5s");
        } catch (InterruptedException e) {
            logger.warn("interrupted while waiting for scheduler engine termination");

    public Set scheduledJobIds() {


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?