Requested thread pool size for is too large; setting to maximum instead – How to solve related issues

Average Read Time

2 Mins

Requested thread pool size for is too large; setting to maximum instead – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Requested thread pool size for is too large; setting to maximum instead ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: pool, thread and threadpool.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

Log “requested thread pool size [{}] for [{}] is too large; setting to maximum [{}] instead” classname is ThreadPool.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if ((name.equals(Names.BULK) || name.equals(Names.INDEX)) && size > availableProcessors) {
            // We use a hard max size for the indexing pools; because if too many threads enter Lucene's IndexWriter; it means
            // too many segments written; too frequently; too much merging; etc:
            // TODO: I would love to be loud here (throw an exception if you ask for a too-big size); but I think this is dangerous
            // because on upgrade this setting could be in cluster state and hard for the user to correct?
            logger.warn("requested thread pool size [{}] for [{}] is too large; setting to maximum [{}] instead";
                        size; name; availableProcessors);
            size = availableProcessors;
        }

        return size;




 

Run the Check-Up to get a customized report like this:

Analyze your cluster