[
https://issues.apache.org/jira/browse/AMBARI-15508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241331#comment-15241331
]
Henning Kropp commented on AMBARI-15508:
----------------------------------------
[~dsen] That is indeed a problem. I just updated the alerts on an exiting
cluster to point to dfs.internal.namservices. Here is the procedure I used:
1. Get ids of all alerts:
{code}
curl -i -k -u admin:admin
"https://<ambari_host>:8080/api/v1/clusters/<cluster_name>/alert_definitions/?AlertDefinition/name=namenode_webui"
for: namenode_hdfs_pending_deletion_blocks, datanode_health_summary,
namenode_directory_status, namenode_hdfs_blocks_health,
namenode_hdfs_capacity_utilization, namenode_rpc_latency, namenode_cpu
{code}
2. Get and update the source of the alerts
3. Push alerts to ambari
If AMBARI-15788 is not taking care of this how can this be included?
Changes to {{TestAlerts.py}} are part of the here provided patch. I'll check,
if I have missed some. Thanks
> Enable HDFS alerts with multiple namservices
> --------------------------------------------
>
> Key: AMBARI-15508
> URL: https://issues.apache.org/jira/browse/AMBARI-15508
> Project: Ambari
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Henning Kropp
> Assignee: Henning Kropp
> Fix For: 2.4.0
>
> Attachments: AMBARI-15508
>
>
> If dfs.namenode.http(s)-address is removed due to HA and multiple
> nameservices are configured NN web alerting reports NN site down.
> Reason seems to be the following alerting configuration:
> {code}
> "high_availability": {
> "nameservice": "{{hdfs-site/dfs.nameservices}}",
> "alias_key" :
> "{{hdfs-site/dfs.ha.namenodes.{{ha-nameservice}}}}",
> "http_pattern" :
> "{{hdfs-site/dfs.namenode.http-address.{{ha-nameservice}}.{{alias}}}}",
> "https_pattern" :
> "{{hdfs-site/dfs.namenode.https-address.{{ha-nameservice}}.{{alias}}}}"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
