Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Wed, 13 Nov 2013 16:05:23 +0000 (UTC)
From: "Tom Beerbower (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12650654.1370271502965.67038.1384358723003@arcas>
In-Reply-To: <JIRA.12650654.1370271502965@arcas>
References: <JIRA.12650654.1370271502965@arcas>
Subject: [jira] [Updated] (AMBARI-2254) Reduce number of requests when
 querying for subtasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tom Beerbower updated AMBARI-2254:
----------------------------------

    Attachment:     (was: AMBARI-2254.patch)

> Reduce number of requests when querying for subtasks
> ----------------------------------------------------
>
>                 Key: AMBARI-2254
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2254
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 1.5.0
>
>
> A query like ...
> /services?fields=components/ServiceComponentInfo,components/host_components,components/host_components/HostRoles
> ... will create multiple requests for resources through the ClusterController. It looks like ClusterController gets called once for all the services, then once for all of the components under each service, then once for all the host_components under each component under each service. So, if there are 10 services that each have 10 components, there will be 100 calls to the ClusterController to get host components, plus 10 calls for the components and another for the services. We should be able to optimize this down to 3 calls... 1 for the services, 1 for the components and 1 for the host_components.


--
This message was sent by Atlassian JIRA
(v6.1#6144)