[
https://issues.apache.org/jira/browse/AMBARI-15508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241311#comment-15241311
]
Dmytro Sen commented on AMBARI-15508:
-------------------------------------
[~hkropp]
I see.
Committed AMBARI-15788, so after upgrade we can rely on
dfs.internal.nameservices, but there is still a problem: updated alert
definitions from patched alerts.json's aren't applied on already installed
clusters. For upgraded clusters it's not enough to patch alert.json's , alert
definitions in ambari DB should be updated as well.
Check this example for hive alerts -
org.apache.ambari.server.upgrade.UpgradeCatalog221#updateAlerts
Unit test ambari/ambari-agent/src/test/python/ambari_agent/TestAlerts.py still
takes nameservice value from dfs.nameservices , I think it should be fixed in
scope of this jira.
> 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)
