ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8622) Alerts UI: Enabling/Disabling alert-definitions takes too long
Date Tue, 09 Dec 2014 23:32:15 GMT

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

Hudson commented on AMBARI-8622:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit-docker #432 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/432/])
AMBARI-8622. Alerts UI: Enabling/Disabling alert-definitions takes too long (sgunturi: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=abff00010279aa64cf36d489f260702206ba4444)
* ambari-web/app/controllers/main/alerts/definition_details_controller.js
* ambari-web/app/controllers/main/alert_definitions_controller.js


> Alerts UI: Enabling/Disabling alert-definitions takes too long
> --------------------------------------------------------------
>
>                 Key: AMBARI-8622
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8622
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8622.patch
>
>
> When Enable/Disable action on an alert-definition is clicked, it takes a good 5 seconds
before it actually happens. Till then user is left in unknown state of whether the action
succeeded. 
> We need to refresh the alert-definition state immediately instead of waiting for next
update cycle.



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

Mime
View raw message