-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63558/#review190149
-----------------------------------------------------------


Ship it!




Ship It!

- Dmitro Lisnichenko


On Nov. 4, 2017, 11:42 a.m., stephane san wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63558/
> -----------------------------------------------------------
> 
> (Updated Nov. 4, 2017, 11:42 a.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/AMBARI-22361
>     
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/AMBARI-22361
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> In the ambari console, a critical alert gets reported for the NameNode Web UI 
> due to mixed cases in hostname
> 
> Error at hand:
> Connection failed to http://vz-sl-upupup-8724-hadoop-mgr-1:0 (<urlopen error 
> [Errno 111] Connection refused>)
> 
> Issue:
> While in HA mode the hdfs-site property
> dfs.namenode.http-address.{{ha-nameservice}}.{{nn_id}}
> may have upper case parts, which prevents matching the hostname.
> The matching should be case insensitive and so both will be
> converted to lower case before the matching is performed.
> 
> Fix:
> lower case before doing the comparison
> (samilar resolution as in https://issues.apache.org/jira/browse/AMBARI-19282)
> 
> 
> Diffs
> -----
> 
>   ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py 05f80234d0 
> 
> 
> Diff: https://reviews.apache.org/r/63558/diff/1/
> 
> 
> Testing
> -------
> 
> Verified the ambari console doesn't report the critical alert any more.
> (the ambari console reports http return code 200 when testing the NameNode 
> Web UI access).
> 
> 
> Thanks,
> 
> stephane san
> 
>

Reply via email to