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




ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_ha_namenode_health.py
 (line 195)
<https://reviews.apache.org/r/50526/#comment209718>

    Looks like now, alert results will come from active, inactive and unknown 
nodes at the same time and not only from active? 
    
    Not sure, if jxm query could be executed fine from all hosts which means 
that result wcould be different from each host. How they would be aggregated 
then?


- Dmytro Grinenko


On July 27, 2016, 7:06 p.m., Jonathan Hurley wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50526/
> -----------------------------------------------------------
> 
> (Updated July 27, 2016, 7:06 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmitro Lisnichenko, Nate 
> Cole, and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-17928
>     https://issues.apache.org/jira/browse/AMBARI-17928
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Name Node High Availability Health alert "response" message is mentioned as 
> "Another host will report this alert".
> 
> STR:
> - Setup NameNode HA
> - Shutdown the standby NameNode
> 
> The text will flip between:
> {{Active['c6402.ambari.apache.org:50070'], Standby[], 
> Unknown['c6401.ambari.apache.org:50070']}}
> and
> {{Another host will report this alert}}
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_ha_namenode_health.py
>  00d1421 
> 
> Diff: https://reviews.apache.org/r/50526/diff/
> 
> 
> Testing
> -------
> 
> Live testing on a cluster.
> 
> 
> Thanks,
> 
> Jonathan Hurley
> 
>

Reply via email to