You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/05/29 13:17:17 UTC

[jira] [Updated] (AMBARI-11528) AlertReceivedListener produces large number of db requests

     [ https://issues.apache.org/jira/browse/AMBARI-11528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen updated AMBARI-11528:
--------------------------------
    Attachment: AMBARI-11528.patch

> AlertReceivedListener produces large number of db requests
> ----------------------------------------------------------
>
>                 Key: AMBARI-11528
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11528
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11528.patch
>
>
> In 5-min snapshot processing of onAlertEvent method took ~94 seconds producing 46k commits and almost same amount of db requests (~equally split between alert_history and alert_definition tables)
> this can be related to large amount to alerts, but it should be addressed as we can have even more alerts on larger clusters, and it can be caused by a single thread only for all listeners, so there's possible bottleneck here.



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