You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Dmitro Lisnichenko <dl...@hortonworks.com> on 2015/04/20 19:15:20 UTC
Review Request 33364: Alerts: nodemanager health is critical,
response is not clear
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33364/
-----------------------------------------------------------
Review request for Ambari and Vitalyi Brodetskyi.
Bugs: AMBARI-10608
https://issues.apache.org/jira/browse/AMBARI-10608
Repository: ambari
Description
-------
5 node cluster, 5 NodeManager
each has NodeManager Health alert instance
All are critical
response is: NodeManager returned an unexpected status of "False"
Not sure what this means.
If I check the ResourceManager, it does seem the NMs are unhealthy. But the alert response doesn't seem to give enough info to know what is going on
Diffs
-----
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/alerts/alert_nodemanager_health.py 516d858
Diff: https://reviews.apache.org/r/33364/diff/
Testing
-------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ...................................... SUCCESS [3.504s]
[INFO] Ambari Metrics Common ............................. SUCCESS [0.781s]
[INFO] Ambari Server ..................................... SUCCESS [39.759s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 44.753s
[INFO] Finished at: Mon Apr 20 20:14:54 EEST 2015
[INFO] Final Memory: 47M/411M
[INFO] ------------------------------------------------------------------------
Thanks,
Dmitro Lisnichenko
Re: Review Request 33364: Alerts: nodemanager health is critical,
response is not clear
Posted by Vitalyi Brodetskyi <vb...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33364/#review80749
-----------------------------------------------------------
Ship it!
Ship It!
- Vitalyi Brodetskyi
On Квітень 20, 2015, 5:15 після полудня, Dmitro Lisnichenko wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/33364/
> -----------------------------------------------------------
>
> (Updated Квітень 20, 2015, 5:15 після полудня)
>
>
> Review request for Ambari and Vitalyi Brodetskyi.
>
>
> Bugs: AMBARI-10608
> https://issues.apache.org/jira/browse/AMBARI-10608
>
>
> Repository: ambari
>
>
> Description
> -------
>
> 5 node cluster, 5 NodeManager
> each has NodeManager Health alert instance
> All are critical
> response is: NodeManager returned an unexpected status of "False"
> Not sure what this means.
> If I check the ResourceManager, it does seem the NMs are unhealthy. But the alert response doesn't seem to give enough info to know what is going on
>
>
> Diffs
> -----
>
> ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/alerts/alert_nodemanager_health.py 516d858
>
> Diff: https://reviews.apache.org/r/33364/diff/
>
>
> Testing
> -------
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views ...................................... SUCCESS [3.504s]
> [INFO] Ambari Metrics Common ............................. SUCCESS [0.781s]
> [INFO] Ambari Server ..................................... SUCCESS [39.759s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 44.753s
> [INFO] Finished at: Mon Apr 20 20:14:54 EEST 2015
> [INFO] Final Memory: 47M/411M
> [INFO] ------------------------------------------------------------------------
>
>
> Thanks,
>
> Dmitro Lisnichenko
>
>