aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1837) Improve implicit task history pruning
Date Fri, 04 Aug 2017 12:48:00 GMT

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

Stephan Erb commented on AURORA-1837:
-------------------------------------

Is this ticket and the associated RB still valid? In AURORA-1929 we have merged a task history
pruning improvement by [~kaih] that might have improved the implicit pruning as well.

> Improve implicit 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.4.14#64029)

Mime
View raw message