[
https://issues.apache.org/jira/browse/AURORA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343265#comment-15343265
]
Bill Farner commented on AURORA-1722:
-------------------------------------
{quote}
The scheduler keeps restarting the failing tasks so we end up accumulating
dozens task statuses per instance.
{quote}
{quote}
How would we get the latest task status that was ran on every aurora instance
{quote}
In case you've been led to believe a {{ScheduledTask}} for an instance that has
been restarted many times will contain task events for multiple restarts. In
case that's the case, i'd like to clarify that each {{ScheduledTask}}
represents a _single attempt_ to execute an instance (initial state -> ... ->
terminal state). Therefore, filtering by active task states will give you what
i _think_ you want (the latest task status).
> 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)
