You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/04/25 00:03:16 UTC
[jira] [Commented] (AMBARI-2022) Service Component metric
collection API takes over a minute on large cluster
[ https://issues.apache.org/jira/browse/AMBARI-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641026#comment-13641026 ]
Siddharth Wagle commented on AMBARI-2022:
-----------------------------------------
+1 patch looks good.
> Service Component metric collection API takes over a minute on large cluster
> ----------------------------------------------------------------------------
>
> Key: AMBARI-2022
> URL: https://issues.apache.org/jira/browse/AMBARI-2022
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Attachments: AMBARI-2022.patch
>
>
> URL:
> http://hor6n01.gq1.ygridcore.net:8080/api/v1/clusters/c1/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
> Multiple data nodes are down, so jmx properties are unavailable.
> eg:http://hor12n28.gq1.ygridcore.net:50075/jmx
> The connection timeout on the JMXPorpertyProvider is -1. This needs to be a finite number
--
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