You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2014/03/14 22:38:45 UTC

[jira] [Assigned] (AURORA-263) Support a min guaranteed task history retention period

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

Maxim Khutornenko reassigned AURORA-263:
----------------------------------------

    Assignee: Maxim Khutornenko

> Support a min guaranteed task history retention period
> ------------------------------------------------------
>
>                 Key: AURORA-263
>                 URL: https://issues.apache.org/jira/browse/AURORA-263
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>
> Task history currently does not deliver any retention guarantees beyond a max of 100 tasks per job over at most 2 days (whichever comes first). This makes any immediate event processing (i.e. SLA monitoring) impossible under heavy turn over. 
> Have the HistoryPrunner support a min configurable retention period (e.g. 2 minutes) to mitigate the above problem. The risk of overloading mem store is minimal due to throttling of flapping tasks.   



--
This message was sent by Atlassian JIRA
(v6.2#6252)