[ https://issues.apache.org/jira/browse/AURORA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341343#comment-15341343
]
Stephan Erb commented on AURORA-1722:
-------------------------------------
If you set {{limit_per_instance}} to 1, you'd get one status result per instance but that
will probably not be the latest status. So, we have to implement a server-side sorting before
applying the limit. Would we adapt the existing {{limit}} filter accordingly and also do server
side sorting when it is used?
> 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)
|