incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-2022) Service Component metric collection API takes over a minute on large cluster
Date Tue, 07 May 2013 22:07:16 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yusaku Sako updated AMBARI-2022:
--------------------------------

    Affects Version/s: 1.2.2
    
> 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
>    Affects Versions: 1.2.2
>            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

Mime
View raw message