You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@ambari.apache.org by Vivek Ratnavel Subramanian <vi...@gmail.com> on 2017/02/08 01:42:07 UTC

Review Request 56420: 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

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56420/
-----------------------------------------------------------

Review request for Ambari, Jaimin Jetly, Richard Zang, Xi Wang, and Yusaku Sako.


Bugs: AMBARI-19907
    https://issues.apache.org/jira/browse/AMBARI-19907


Repository: ambari


Description
-------

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.


Diffs
-----

  ambari-web/app/controllers/main/host/bulk_operations_controller.js 0e73c0c 
  ambari-web/app/controllers/main/host/details.js f040db5 
  ambari-web/app/controllers/main/service.js e434d41 
  ambari-web/app/controllers/main/service/item.js 6f1efd8 
  ambari-web/app/utils/ajax/ajax.js 2ea6113 
  ambari-web/app/utils/batch_scheduled_requests.js b8ae955 
  ambari-web/test/controllers/main/service_test.js d8c3365 

Diff: https://reviews.apache.org/r/56420/diff/


Testing
-------

Verified Manually.
Ambari-web unit tests pass.
30312 passing (19s)
157 pending


Thanks,

Vivek Ratnavel Subramanian


Re: Review Request 56420: 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

Posted by Vivek Ratnavel Subramanian <vi...@gmail.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56420/
-----------------------------------------------------------

(Updated Feb. 9, 2017, 2:52 a.m.)


Review request for Ambari, Jaimin Jetly, Richard Zang, Xi Wang, and Yusaku Sako.


Changes
-------

Added a latency of 200ms before Loading popup shows up.


Bugs: AMBARI-19907
    https://issues.apache.org/jira/browse/AMBARI-19907


Repository: ambari


Description
-------

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.


Diffs (updated)
-----

  ambari-web/app/controllers/main/host/bulk_operations_controller.js 0e73c0c 
  ambari-web/app/controllers/main/host/details.js f040db5 
  ambari-web/app/controllers/main/service.js e434d41 
  ambari-web/app/controllers/main/service/item.js 6f1efd8 
  ambari-web/app/utils/ajax/ajax.js 2ea6113 
  ambari-web/app/utils/batch_scheduled_requests.js b8ae955 
  ambari-web/test/controllers/main/service_test.js d8c3365 

Diff: https://reviews.apache.org/r/56420/diff/


Testing
-------

Verified Manually.
Ambari-web unit tests pass.
30312 passing (19s)
157 pending


Thanks,

Vivek Ratnavel Subramanian