Max running job capacity ” + localMaxAllowedRunningJobs + ” reached – Elasticsearch Error How To Solve Related Issues


Max running job capacity ” + localMaxAllowedRunningJobs + ” reached – Elasticsearch Error How To Solve Related Issues

Opster Team

July-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 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. 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: plugin.

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

Log”max running job capacity [” + localMaxAllowedRunningJobs + “] reached”classname  is AutodetectProcessManager.java 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";
  RestStatus.TOO_MANY_REQUESTS);
  }
 
  String jobId = jobTask.getJobId();
  notifyLoadingSnapshot(jobId; autodetectParams);

 

Optimize Elasticsearch Performance

Try The Tool