[
https://issues.apache.org/jira/browse/AURORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner resolved AURORA-106.
--------------------------------
Resolution: Won't Fix
Proceeding with AURORA-334 instead.
> Create a new task store with a hierarchical structure for storing tasks.
> ------------------------------------------------------------------------
>
> Key: AURORA-106
> URL: https://issues.apache.org/jira/browse/AURORA-106
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Bill Farner
> Priority: Minor
>
> The hierarchical structure will be the crux of the new task store.
> The primary goals are:
> 1. Reduce heap
> 2. Reduce snapshot size.
> 3. Better api for queries and prevent going through the entire task store.
> Proposed hierarchy is:
> Role > Env > Job > Instance > Generation > Task
> Much of what is currently stored in the TaskConfig would move to Generation,
> and a goal would be to prevent or at least reduce redundant information.
> This also involved a composed key structure, where a RoleKey is a string, an
> EnvKey is a string and a RoleKey, and so on.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
