[ 
https://issues.apache.org/jira/browse/AMBARI-18407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494762#comment-15494762
 ] 

Hadoop QA commented on AMBARI-18407:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12828708/AMBARI-18047.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 4 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 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8687//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8687//console

This message is automatically generated.

> BE: /api/v1/persist/CLUSTER_CURRENT_STATUS takes more than 2s for 
> transferring 307KB response
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18407
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18407
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-18047.patch
>
>
> Ambari UI when logging-in requests the persisted cluster status from the 
> /api/v1/persist/CLUSTER_CURRENT_STATUS call. On a 800 node cluster this takes 
> 2s or more to GET.
> The majority of time is in the transfer of bytes. 
> A 3.8s call had a wait time (time to first byte) of 815ms, and content 
> download time of 2.98s.
> We need to see if the download time can be improved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to