aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Morozov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1722) Add new field to TaskQuery to allow querying latest statuses grouped by instance id
Date Wed, 22 Jun 2016 21:20:16 GMT

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

Igor Morozov commented on AURORA-1722:
--------------------------------------

How about the following idea that would be similar to what Maxim is proposing. If there are
non empty instance_ids in a task query we would change the semantic of that call a little
bit and try to fill in all instances id's task statuses first until we hit the limit.

> Add new field to TaskQuery to allow querying latest statuses grouped by instance id
> -----------------------------------------------------------------------------------
>
>                 Key: AURORA-1722
>                 URL: https://issues.apache.org/jira/browse/AURORA-1722
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>    Affects Versions: 0.16.0
>            Reporter: Igor Morozov
>
> Currently in order to get the status of all job instances both failed and running one
needs to issue a query for all task statuses, then group them by instance id and sort by timestamp
to get the lastest statuses per instance. 
> For tasks with a lot of churn that may cause unnecessary transferring huge blobs of thrifts.

> The proposal is to include new member into TaskQuery struct
> struct TaskQuery {
> ...
>   14: i32 limit_per_instance
> }



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

Mime
View raw message