[
https://issues.apache.org/jira/browse/AMBARI-20016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866704#comment-15866704
]
Hadoop QA commented on AMBARI-20016:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852651/AMBARI-20016.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 11 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/10572//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10572//console
This message is automatically generated.
> Hosts page moving through pages gets progressively slower to the point of
> being unusable
> ----------------------------------------------------------------------------------------
>
> Key: AMBARI-20016
> URL: https://issues.apache.org/jira/browse/AMBARI-20016
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20016_branch-2.5.patch, AMBARI-20016.patch
>
>
> STR:
> * On a 1000-node cluster, go to Hosts page
> * Set the page size to 100 (shows hosts 1-100)
> * Using the paging controls, go to the next page (shows hosts 101-200) - this
> takes several seconds
> * Using the paging controls, go to the next page (shows hosts 201-300) - this
> takes longer
> * Repeat showing the next set of hosts. This gets progressively slower. I
> gave up when I hit 701-800 since the page got totally stuck after waiting for
> 3 minutes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
