[
https://issues.apache.org/jira/browse/AURORA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343026#comment-15343026
]
Igor Morozov edited comment on AURORA-1722 at 6/21/16 11:27 PM:
----------------------------------------------------------------
What would be the scope of this limit? I think it is wired now in a way that I
can limit the output but it doesn't guarantee I receive at least one status
update per instance and the order of those events is not defined. That means
that I may need to scroll through lots of task updates to collect latest
statuses for all instances in a job.
was (Author: igmorv):
What would be the scope of this limit? I think it is wired now in a way that I
can limit the output but it doesn't guarantee I receive at least one status
update per instance and the order of those events is uncertain. That means that
I may need to scroll through lots of task updates to collect latest statuses
for all instances in a job.
> 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)
