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

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-11528:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12736115/AMBARI-11528.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2923//console

This message is automatically generated.

> 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)