ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8118) HostComponent requests that include Nagios are not performant
Date Mon, 03 Nov 2014 20:24:34 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195032#comment-14195032
] 

Hudson commented on AMBARI-8118:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #814 (See [https://builds.apache.org/job/Ambari-trunk-Commit/814/])
AMBARI-8118.  HostComponent requests that include Nagios are not performant (ncole) (ncole:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=08101e4300d9d1c7093ca0e32ff3ba38d00f84bf)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HttpProxyPropertyProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/HttpPropertyProviderTest.java


> HostComponent requests that include Nagios are not performant
> -------------------------------------------------------------
>
>                 Key: AMBARI-8118
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8118
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-8118.patch
>
>
> Requests like the following take a long time to process on large clusters.
> This call includes asking Nagios for alert data, when that data is never used.  This
information now comes from the NagiosPropertyProvider class, not the HttpProxyPropertyProvider
class.
> http://localhost:8080/api/v1/clusters/c/components/?ServiceComponentInfo/category=MASTER&fields=ServiceComponentInfo/Version,ServiceComponentInfo/StartTime,ServiceComponentInfo/HeapMemoryUsed,ServiceComponentInfo/HeapMemoryMax,ServiceComponentInfo/service_name,host_components/HostRoles/host_name,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/ha_state,host_components/metrics/jvm/memHeapUsedM,host_components/metrics/jvm/HeapMemoryMax,host_components/metrics/jvm/HeapMemoryUsed,host_components/metrics/jvm/memHeapCommittedM,host_components/metrics/mapred/jobtracker/trackers_decommissioned,host_components/metrics/cpu/cpu_wio,host_components/metrics/rpc/RpcQueueTime_avg_time,host_components/metrics/dfs/FSNamesystem/*,host_components/metrics/dfs/namenode/Version,host_components/metrics/dfs/namenode/DecomNodes,host_components/metrics/dfs/namenode/TotalFiles,host_components/metrics/dfs/namenode/UpgradeFinalized,host_components/metrics/dfs/namenode/Safemode,host_components/metrics/runtime/StartTime,host_components/metrics/flume/flume,host_components/processes/HostComponentProcess,host_components/metrics/hbase/master/IsActiveMaster,ServiceComponentInfo/MasterStartTime,ServiceComponentInfo/MasterActiveTime,ServiceComponentInfo/AverageLoad,ServiceComponentInfo/Revision,ServiceComponentInfo/RegionsInTransition,metrics/api/v1/cluster/summary,metrics/api/v1/topology/summary,host_components/metrics/yarn/Queue,ServiceComponentInfo/rm_metrics/cluster/activeNMcount,ServiceComponentInfo/rm_metrics/cluster/unhealthyNMcount,ServiceComponentInfo/rm_metrics/cluster/rebootedNMcount,ServiceComponentInfo/rm_metrics/cluster/decommissionedNMcount&minimal_response=true



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message