Log Requested thread pool size for is too large; setting to maximum instead – How To Solve Related Issues



Log 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 try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

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, 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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

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;




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 ElasticSearch gives error about queue size -views 33.58 K ,score 26

Logstash Isn’t Authenticating With Elasticsearch Shield -views   0.67 K,score 1

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now