ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Beerbower (JIRA)" <>
Subject [jira] [Reopened] (AMBARI-3583) Requests API should rollup tasks information
Date Wed, 30 Oct 2013 14:57:28 GMT


Tom Beerbower reopened AMBARI-3583:

> Requests API should rollup tasks information
> --------------------------------------------
>                 Key: AMBARI-3583
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 1.4.2
>         Attachments: AMBARI-3583-2.patch, AMBARI-3583.patch
> Ambari UI shows the number of background-operations. Clicking on it launches a dialog
showing the progress/status of each request. We keep polling every 6s at the following URL:
> {code}
> http://server:8080/api/v1/clusters/ga/requests?to=end&page_size=10&fields=*,tasks/Tasks/*
> {code}
> On large clusters this is really really huge if you restarted services multiple times.
All of this just to show the number of operations in progress, and the status of each request.
> We need a rollup of tasks data into the request itself, so that we dont load the tasks
(the heavy part) till details of a request are needed. So for each request we need 
> * Progress of the request: This takes into account the progress of various tasks. 100%
means request is completed. 
> * State of the request: Depending on success/warn/failure of tasks, this will help UI
show a red/green/yellow for the entire request.
> Our initial call will be to
> {code}
> http://server:8080/api/v1/clusters/ga/requests?to=end&page_size=10
> {code}
> Once a user drills into a request, we will be requesting entire details for it.
> {code}
> http://server:8080/api/v1/clusters/ga/requests/1?fields=tasks/Tasks/*
> {code}

This message was sent by Atlassian JIRA

View raw message