You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2013/06/04 23:17:21 UTC
[jira] [Updated] (AMBARI-2245) Alerts not showing up for YARN and
MR2 services
[ https://issues.apache.org/jira/browse/AMBARI-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate Cole updated AMBARI-2245:
------------------------------
Attachment: AMBARI-2245.patch
> Alerts not showing up for YARN and MR2 services
> -----------------------------------------------
>
> Key: AMBARI-2245
> URL: https://issues.apache.org/jira/browse/AMBARI-2245
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.4.0
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 1.4.0
>
> Attachments: AMBARI-2245.patch, AMBARI-2245.patch
>
>
> There are no alerts shown for YARN or MR2 services. Maybe in UI we are not checking specifically for their IDs.
> Today I got cluster on the using VM.
> Yes, server returns errors for new services, but service_type of them is "UNKNOWN". So, they can't be "assigned" to some service.
> Example:
> {code}
> {
> "service_description" : "Node Manager process down",
> "host_name" : "dev01",
> "current_attempt" : "3",
> "current_state" : "2",
> "plugin_output" : "Connection refused",
> "last_hard_state_change" : "1369918750",
> "last_hard_state" : "2",
> "last_time_ok" : "1369918630",
> "last_time_warning" : "0",
> "last_time_unknown" : "0",
> "last_time_critical" : "1369929310",
> "is_flapping" : "0",
> "last_check" : "1369929310",
> "service_type" : "UNKNOWN"
> },
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira