You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2013/08/02 14:57:49 UTC

[jira] [Commented] (AMBARI-2786) YARN time series data needed for NodeManager statuses

    [ https://issues.apache.org/jira/browse/AMBARI-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727648#comment-13727648 ] 

Andrew Onischuk commented on AMBARI-2786:
-----------------------------------------

[~sgunturi], the same we have with some of queue mertics, they are not filled, until, first time changed from zero, you can take a look at that ticket:
https://issues.apache.org/jira/browse/AMBARI-2244
This is ok, since we know it's zero if no yet timeseries available

Here what Nate Cole, said about it:
??On the queue metrics: many of them are apparently filled in when they are accessed for the first time, so it might be prudent for the UI to assume zero if the properties are not there at all.??
                
> YARN time series data needed for NodeManager statuses
> -----------------------------------------------------
>
>                 Key: AMBARI-2786
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2786
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.0
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 1.4.0
>
>         Attachments: AMBARI-2786.patch
>
>
> We need API call for a graph which will show NodeManager status counts. NodeManagers can be in the following states: active, lost, unhealthy, rebooted, and decommissioned.

--
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