You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2014/04/30 19:48:16 UTC
[jira] [Created] (AMBARI-5639) Ambari Server will not respond to
HTTP connections if server has high number of CPUs which exceed number of
Jetty threads (25)
Nate Cole created AMBARI-5639:
---------------------------------
Summary: Ambari Server will not respond to HTTP connections if server has high number of CPUs which exceed number of Jetty threads (25)
Key: AMBARI-5639
URL: https://issues.apache.org/jira/browse/AMBARI-5639
Project: Ambari
Issue Type: Task
Components: controller
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 1.6.1
AmbariServer defines thread pool size via:
serverForAgent.setThreadPool(new QueuedThreadPool(25));
server.setThreadPool(new QueuedThreadPool(25));
The values for the thread pool should be pulled via configuration. Add the two properties for:
{noformat}
client.threadpool.size.max
agent.threadpool.size.max
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)