[
https://issues.apache.org/jira/browse/AURORA-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner updated AURORA-743:
-------------------------------
Assignee: Maxim Khutornenko
> Figure out retention policy for scheduler job update data
> ---------------------------------------------------------
>
> Key: AURORA-743
> URL: https://issues.apache.org/jira/browse/AURORA-743
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Maxim Khutornenko
>
> We need to come up with job update history retention policy sooner than later
> to avoid tipping over the snapshot creation timeout (large heap data ==
> longer GC times == failover). Perhaps going after the Task retention approach
> (N items per job) is the easiest until we have a durable DB storage/backups
> and can afford longer history (e.g. time-based purging or infinite archive).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
