[jira] [Updated] (AMBARI-19907) 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
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19907: --- Fix Version/s: 2.4.3 > 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, 2.4.3 > > Attachments: AMBARI-19907_branch-2.5_final.patch, > AMBARI-19907_fix1.patch, AMBARI-19907_trunk_final.patch, > AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.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)
[jira] [Updated] (AMBARI-19907) 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
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19907: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 424949b95cafead9754cd87ea1a379f21995b5af > 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_branch-2.5_final.patch, > AMBARI-19907_fix1.patch, AMBARI-19907_trunk_final.patch, > AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.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)
[jira] [Updated] (AMBARI-19907) 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
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19907: -- Attachment: AMBARI-19907_trunk_final.patch AMBARI-19907_branch-2.5_final.patch > 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_branch-2.5_final.patch, > AMBARI-19907_fix1.patch, AMBARI-19907_trunk_final.patch, > AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.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)
[jira] [Updated] (AMBARI-19907) 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
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19907: -- Attachment: AMBARI-19907_fix1.patch > 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_fix1.patch, > AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.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)
[jira] [Updated] (AMBARI-19907) 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
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Attachment: AMBARI-19907.v1.patch > 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, AMBARI-19907.v1.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)
[jira] [Updated] (AMBARI-19907) 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
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Status: Patch Available (was: In Progress) > 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)
[jira] [Updated] (AMBARI-19907) 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
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Attachment: AMBARI-19907.v0.branch-2.5.patch > 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)
