You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mehrdad Nurolahzade (JIRA)" <ji...@apache.org> on 2017/02/10 17:02:41 UTC

[jira] [Assigned] (AURORA-1837) Improve task history pruning

     [ https://issues.apache.org/jira/browse/AURORA-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mehrdad Nurolahzade reassigned AURORA-1837:
-------------------------------------------

    Assignee: Mehrdad Nurolahzade

> Improve task history pruning
> ----------------------------
>
>                 Key: AURORA-1837
>                 URL: https://issues.apache.org/jira/browse/AURORA-1837
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Reza Motamedi
>            Assignee: Mehrdad Nurolahzade
>            Priority: Minor
>              Labels: scheduler
>
> Current implementation of {{TaskHistoryPrunner}} registers all inactive tasks upon terminal _state_ change for pruning. {{TaskHistoryPrunner::registerInactiveTask()}} uses a delay executor to schedule the process of pruning _task_s. However, we have noticed most of pruning takes place after scheduler recovers from a fail-over.
> Modify {{TaskHistoryPruner}} to a design similar to {{JobUpdateHistoryPruner}}:
> # Instead of registering delay executor's upon terminal task state transitions, have it wake up on preconfigured intervals, find all terminal state tasks that meet pruning criteria and delete them.
> # Make the initial task history pruning delay configurable so that it does not hamper scheduler upon start.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)