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

Ship it!


Let's make sure we want this to be for all stacks since it's at the 
common-services level.


ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json 
(line 216)
<https://reviews.apache.org/r/38062/#comment153399>

    Most of our metric alerts are 5. I have no problem with this being 2, but I 
just want to ensure it's right.



ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json 
(line 238)
<https://reviews.apache.org/r/38062/#comment153400>

    Maybe run this by Jeff Sposetti: did we want to make this more human 
readable? Something like
    
    There are {0} block(s) pending deletion.


- Jonathan Hurley


On Sept. 2, 2015, 1:04 p.m., Vitalyi Brodetskyi wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38062/
> -----------------------------------------------------------
> 
> (Updated Sept. 2, 2015, 1:04 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-12980
>     https://issues.apache.org/jira/browse/AMBARI-12980
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Alert Type = METRIC
> Lets add a new Alert for HDFS based on PendingDeletionBlocks. This is a JMX 
> data point FSNamesystem --> PendingDeletionBlocks.
> This alert could potentially be designed based on NameNode Blocks Health. 
> Warning and Critical both can be issued when the value exceeds 100,000. These 
> thresholds should be configurable.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json 
> 477fd95 
> 
> Diff: https://reviews.apache.org/r/38062/diff/
> 
> 
> Testing
> -------
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Reply via email to