[
https://issues.apache.org/jira/browse/AURORA-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner updated AURORA-154:
-------------------------------
Priority: Trivial (was: Minor)
> Consider supporting multiple tasks per executor
> -----------------------------------------------
>
> Key: AURORA-154
> URL: https://issues.apache.org/jira/browse/AURORA-154
> Project: Aurora
> Issue Type: Epic
> Components: Executor
> Reporter: brian wickman
> Priority: Trivial
>
> Support multiple tasks per executor; decouple lifecycle of task from
> lifecycle of executor.
> Thermos gives the ability to colocate multiple related processes together
> within a single task, however you cannot update these processes independently
> of the task.
> If we could decouple the lifecycle of a task from the lifecycle of the
> executor and/or support multiple tasks within a single executor (and hence
> its cgroup), we could explore more interesting use-cases such as being able
> to update tasks while keeping the sandbox intact. This would be useful for
> heavily stateful services, especially if we can eventually provide stronger
> guarantees about the lifecycle of the executor (e.g. if mesos ever supports
> executors that persist across machine restarts / task loss.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
