[AMBARI-14729] API does not return host component metrics (except for one host)

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.2.1
• Assignee: Siddharth Wagle
• Reporter: Siddharth Wagle
• Created: 19/Jan/16 21:47
• Updated: 27/Jan/16 00:42
• Resolved: 27/Jan/16 00:42

Description

API does not return metrics at the host component level (except for one host).

STR.
Make a metrics API against various hosts for a specific metric.
Example on a 3-node cluster:
Call 1: http://172.22.89.227:8080/api/v1/clusters/c1/hosts/sid-ams-3.novalocal/host_components/DATANODE?fields=metrics/load/load_five[1453147641,1453169241,15]

This returns the metrics on sid-ams-3.

Call 2: http://172.22.89.227:8080/api/v1/clusters/c1/hosts/sid-ams-2.novalocal/host_components/DATANODE?fields=metrics/load/load_five[1453147641,1453169241,15]

This returns no metrics data.

Call 3: http://172.22.89.227:8080/api/v1/clusters/c1/hosts/sid-ams-1.novalocal/host_components/DATANODE?fields=metrics/load/load_five[1453147641,1453169241,15]

This returns no metrics data.

The example above is for a system metric, but the same behavior is exhibited for service metrics.

For any given host component metric, only one of the hosts returns any metric. The first host that you make a query against will return the metrics data, but none of the other hosts.
This is because of the cache implementation.

Issue Links

• links to: Review board