ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Beerbower (JIRA)" <>
Subject [jira] [Commented] (AMBARI-2553) Delay between service tab opening and displaying actual states of "Stop"/"Start" buttons
Date Wed, 03 Jul 2013 17:38:22 GMT


Tom Beerbower commented on AMBARI-2553:

The attached patch makes returning the last N requests possible with this API ...


Details ...
Parameter        Description
page_size        the number of resources to be returned for the paged response
from             the starting page resource (inclusive).  Valid values are 'start' | <offset>
to               the ending page resource (inclusive).  Valid values are 'end' | <offset>

Either from or to should be specified, not both.  If neither is specified then 'from=start'
is assumed.

<offset> is an integer value that represents an offset (zero based) into the set of
resources.  For example, '&from=7' means that the first resource of the response page
should be the 7th resource of the resource set.

'start' indicates an offset of 0.
'end' indicates an offset of the end of the set of resources.

Default ordering (by key properties) is implied.


> Delay between service tab opening and displaying actual states of "Stop"/"Start" buttons
> ----------------------------------------------------------------------------------------
>                 Key: AMBARI-2553
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>         Attachments: AMBARI-2553.patch
> Sometimes, there are displayed not correct status for "Start"/"Stop" buttons during 5-7
seconds after service tab opening.
> This bug was reproduced on SUSE-11 and RHEL-6.3 (HDP-1.3.0).
> This is happening due to long time of getting "background operations" data (huge array
of data). We need this data to determine status of "service buttons" (Start/Stop/SmokeTest).
Currently we  have no opportunity to get from API only 10 last requests, we are receiving
all requests, in some cases it`s huge array of data.
> Now we are using this request:
> {noformat}
> /api/v1/clusters/cl1/requests?fields=tasks/*
> returns all requests with any statuses
> {noformat}
> If we try this one, result is the same: 
> {noformat}
> api/v1/clusters/cl1/requests?Requests/,IN_PROGRESS,FAILED)&fields=tasks/*
> returns all requests with any statuses
> {noformat}
> We need an API to return only last 10 requests, not all.

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:

View raw message