[
https://issues.apache.org/jira/browse/AMBARI-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739606#comment-14739606
]
Hadoop QA commented on AMBARI-13059:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12755150/AMBARI-13059.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/3764//console
This message is automatically generated.
> 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)
