[
https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857892#comment-15857892
]
Hadoop QA commented on AMBARI-19907:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851532/AMBARI-19907.v0.branch-2.5.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
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10454//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10454//console
This message is automatically generated.
> On certain actions, there's no feedback from the UI when API takes a long
> time to respond - not reassuring and the user is encouraged to keep
> triggering the same heavy action to make the problem worse
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-19907
> URL: https://issues.apache.org/jira/browse/AMBARI-19907
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.0
> Reporter: Vivek Ratnavel Subramanian
> Assignee: Vivek Ratnavel Subramanian
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19907.v0.branch-2.5.patch
>
>
> On a big cluster, it takes the server a long time to process the API request
> for certain operations, like "Stop All", "Start All", etc.
> On a small cluster, the "background operations" popup appears within a few
> seconds to acknowledge to the user that the server is working on handling the
> request.
> However, when the cluster gets bigger and the request API takes the server
> much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no
> indication on the UI that the server received the request. This is not
> reassuring to the user and the user is tempted to keep re-triggering the
> action and overwhelming the server.
> This problem is not just for "Start All", "Stop All". This problem actually
> happens for "Stop" and "Start" of a single service as well (and likely other
> places, like Hosts / Host Detail pages.) On the 1000-node cluster, this
> takes about 6-7 seconds, enough to make the user wonder if the request got to
> the server or not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
