[
https://issues.apache.org/jira/browse/AMBARI-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660729#comment-13660729
]
Tom Beerbower commented on AMBARI-2158:
---------------------------------------
In a large cluster we could have hundreds or thousands of resources to populate
in the JMX property provider for a single request. The JMX source for each
resource is potentially a different host in the cluster which means hundreds or
thousands of requests for JMX metrics. Rather than populating the resources
serially, we should distribute the work across multiple threads.
> Certain queries with metrics takes a long time (3 minutes on a 450-node
> cluster)
> --------------------------------------------------------------------------------
>
> Key: AMBARI-2158
> URL: https://issues.apache.org/jira/browse/AMBARI-2158
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
>
> On a 450-node cluster, the following query takes 3 minutes to respond:
> *
> /services?fields=components/ServiceComponentInfo,components/host_components,components/host_components/HostRoles,components/host_components/metrics/jvm/memHeapUsedM,components/host_components/metrics/jvm/memHeapCommittedM,components/host_components/metrics/mapred/jobtracker/trackers_decommissioned
> The following query (only one metric) took 2.7 minutes:
> *
> /services?fields=components/ServiceComponentInfo,components/host_components,components/host_components/HostRoles,components/host_components/metrics/jvm/memHeapUsedM
> Note that the same query without the metrics only takes about 4 seconds:
> *
> /services?fields=components/ServiceComponentInfo,components/host_components,components/host_components/HostRoles
--
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
