[jira] [Updated] (AMBARI-13059) Alerts: HDFS Finalized alert needs to be for HDFS service

["Dmitry Lysnichenko (JIRA)" <ji...@apache.org>]

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

Dmitry Lysnichenko updated AMBARI-13059:
----------------------------------------
    Attachment: AMBARI-13059.patch

> Alerts: HDFS Finalized alert needs to be for HDFS service
> ---------------------------------------------------------
>
>                 Key: AMBARI-13059
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13059
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-13059.patch
>
>
> Why is the HDFS finalized alert an ambari server alert? And not HDFS, for the NameNode? Could it be SCRIPT alert, or metric alert on HDFS? Just seems very strange to be on AMbari server, because then it always getting registered, even in clusters w/o HDFS.
> {code}
> {
>   "href" : "http://server:8080/api/v1/clusters/MyCluster/alert_definitions/40",
>   "AlertDefinition" : {
>     "cluster_name" : "MyCluster",
>     "component_name" : "AMBARI_SERVER",
>     "description" : "This service-level alert is triggered if HDFS is not in the finalized state",
>     "enabled" : true,
>     "id" : 40,
>     "ignore_host" : false,
>     "interval" : 10,
>     "label" : "HDFS Upgrade Finalized State",
>     "name" : "ambari_upgrade_finalized_state",
>     "scope" : "SERVICE",
>     "service_name" : "AMBARI",
>     "source" : {
>       "class" : "org.apache.ambari.server.alerts.HDFSUpgradeFinalizedStatusRunnable",
>       "type" : "SERVER"
>     }
>   }
> }
> {code}



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