[
https://issues.apache.org/jira/browse/AMBARI-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832613#comment-13832613
]
Tom Beerbower commented on AMBARI-3880:
---------------------------------------
Two issues here ...
1) It looks like the order of the property providers changed. This uncovered
an issue with the JMX provider where it wasn't checking for a temporal request.
It should ignore those but was instead treating them as point in time and
overwriting the temporal results from Ganglia.
2) Typo in the setup of the StackDefinedPropertyProvider for Component
resources. Have to pass null for the hostname property since hostname can not
be obtained from a component resource directly.
> HDFS and HBase time series and other data are not coming thru via API
> ---------------------------------------------------------------------
>
> Key: AMBARI-3880
> URL: https://issues.apache.org/jira/browse/AMBARI-3880
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Attachments: AMBARI-3880.patch
>
>
> None of the HDFS time-series data are coming thru via the API (see
> hdfs-graphs.png). The lines look flat because the API is returning a single
> data point, not time-series data. Ganglia Web shows that these time-series
> data are being collected charts.
> For example:
> {noformat}
> http://162.216.148.99:8080/api/v1/clusters/yusaku/hosts/yusaku-1.c.pramod-thangali.internal/host_components/NAMENODE?fields=metrics/dfs/FSNamesystem/CapacityRemainingGB[1385164205,1385167805,15],metrics/dfs/FSNamesystem/CapacityUsedGB[1385164205,1385167805,15],metrics/dfs/FSNamesystem/CapacityTotalGB[1385164205,1385167805,15]&_=1385167804711
> {noformat}
> Result:
> {noformat}
> "metrics" : {
> "jvm" : {
> "memHeapCommittedM" : 57.0625,
> "memHeapUsedM" : 13.249222,
> "memNonHeapCommittedM" : 44.9375,
> "memNonHeapUsedM" : 44.63601
> }
> }
> {noformat}
> Same problem exists for HBase time-series data.
> Also, YARN and HBase summary panels are incorrectly showing n/a, "Not
> Running", etc.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
