Max running job capacity ” + localMaxAllowedRunningJobs + ” reached – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

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

This guide will help you check for common problems that cause the log ” max running job capacity ” + localMaxAllowedRunningJobs + ” reached ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “max running job capacity [” + localMaxAllowedRunningJobs + “] reached”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// Closing jobs can still be using some or all threads in MachineLearning.JOB_COMMS_THREAD_POOL_NAME
 // that an open job uses; so include them too when considering if enough threads are available.
 int currentRunningJobs = processByAllocation.size();
 // TODO: in future this will also need to consider jobs that are not anomaly detector jobs
 if (currentRunningJobs > localMaxAllowedRunningJobs) {
 throw new ElasticsearchStatusException("max running job capacity [" + localMaxAllowedRunningJobs + "] reached";
 String jobId = jobTask.getJobId();
 notifyLoadingSnapshot(jobId; autodetectParams);


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content