Normalization discarded as threadpool is shutting down – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.17-8.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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is trying to normalize data but the threadpool, which is responsible for managing concurrent tasks, is in the process of shutting down. This could be due to a server shutdown or a problem with the Elasticsearch service. To resolve this issue, you can try restarting the Elasticsearch service, ensuring that the server has sufficient resources to handle the tasks, or checking the Elasticsearch configuration for any issues with the threadpool settings.

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 ” [{}] Normalization discarded as threadpool is shutting down ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, threadpool.

Log Context

Log “[{}] Normalization discarded as threadpool is shutting down” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            } catch (RejectedExecutionException e) {
                latestQuantilesHolder = null;
                latestTask = null;
                logger.warn("[{}] Normalization discarded as threadpool is shutting down"; jobId);
                return false;
            return true;
        return false;


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