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:20:17 UTC

[jira] [Assigned] (AMBARI-5273) Web UI does not work when CPUs > 64

     [ https://issues.apache.org/jira/browse/AMBARI-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Cole reassigned AMBARI-5273:
---------------------------------

    Assignee: Nate Cole

> Web UI does not work when CPUs > 64
> -----------------------------------
>
>                 Key: AMBARI-5273
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5273
>             Project: Ambari
>          Issue Type: Improvement
>          Components: controller
>    Affects Versions: 1.4.4
>         Environment: CentOS 5/6
>            Reporter: Lei Xiang
>            Assignee: Nate Cole
>            Priority: Minor
>              Labels: patch, performance
>             Fix For: 1.4.4
>
>         Attachments: AMBARI-5273.patch
>
>
> Ambari Web UI threads blocked when Server CPUs > 64, So the web ui will not response any thing till the browser timeout. In ambari-server.log it will logging a "Insufficient Threads configuration" It's should be a Jetty container bug.
> So I change the ambari-server/src/main/org/apache/ambari/server/controller/AmbariServer.java
>       serverForAgent.setThreadPool(new QueuedThreadPool(25));
>       server.setThreadPool(new QueuedThreadPool(25));
> to 
>       serverForAgent.setThreadPool(new QueuedThreadPool(65));
>       server.setThreadPool(new QueuedThreadPool(65));



--
This message was sent by Atlassian JIRA
(v6.2#6252)