[
https://issues.apache.org/jira/browse/AMBARI-15508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241210#comment-15241210
]
Henning Kropp commented on AMBARI-15508:
----------------------------------------
Can you please explain in what kind of scenario this would be the case?
With the introduction of {{dfs.internal.nameservices}} all alerts using
{{dfs.nameservices}} need to use {{dfs.internal.nameservices}}. Clusters not
yet using {{dfs.internal.nameservices}} need to populate this during the
upgrade process, that should be reflected in AMBARI-15788
If there is no dfs.nameservices in hdfs-site, as your are suggesting, this is
not a HA cluster and {{hdfs-site/dfs.namenode.http-address}} or
{{hdfs-site/dfs.namenode.https-address}}
> 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)
