Srimanth Gunturi created AMBARI-3086:
----------------------------------------

             Summary: Services API call with metrics takes 30% longer with all 
services started
                 Key: AMBARI-3086
                 URL: https://issues.apache.org/jira/browse/AMBARI-3086
             Project: Ambari
          Issue Type: Task
          Components: controller
    Affects Versions: 1.4.0
            Reporter: Srimanth Gunturi


I stopped all the services and started invoking the /services endpoint. While 
that was looping, I invoked the 'Start all services' call. The time being taken 
by the same call increased now by over 30%.

The exact /services call made was 
{noformat}
/api/v1/clusters/${cluster}/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,components/host_components/metrics/cpu/cpu_wio,components/host_components/metrics/rpc/RpcQueueTime_avg_time,components/host_components/metrics/flume/flume,components/host_components/metrics/yarn/Queue
{noformat}

Time measurements in milliseconds:
{noformat}
/services       All Stopped     All Started
Total Time      2100.704545     2926.313725
Latency Time    2048.295455     2838.764706
Transfer Time   52.40909091     87.54901961
Data size (bytes)       825555  1371548
{noformat}

--
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

Reply via email to