[
https://issues.apache.org/jira/browse/AMBARI-12313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617003#comment-14617003
]
Hadoop QA commented on AMBARI-12313:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12743961/AMBARI-12313.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3353//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3353//console
This message is automatically generated.
> Service config pages load extremely slowly (especially on big clusters)
> -----------------------------------------------------------------------
>
> Key: AMBARI-12313
> URL: https://issues.apache.org/jira/browse/AMBARI-12313
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12313.patch
>
>
> The following load time of the service config pages were observed on a 800+
> node cluster:
> HDFS: 36s
> MAPREDUCE2: 32s
> YARN: 35s
> HIVE: 32s
> HBASE: 30s
> Ambari Web makes a number of API calls, but majority of the time is spent on
> UI-side processing. We need to see what we can optimize.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
