[
https://issues.apache.org/jira/browse/MESOS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988277#comment-13988277
]
Niklas Quarfot Nielsen commented on MESOS-1279:
-----------------------------------------------
Sounds great! Go for it. Containerizers have to support Containerizer::update()
- it's a part of the usual flow of:
1) runTask comes in.
2) If executor is not running, start it in a container. (Only with the
resources given to start the executor)
3) Meanwhile, add task as pending on executor.
4) Executor registers with the slave and receive the task (Updates container
resources to contain executor + task)
Or did I misunderstand your concern?
> Add resize task primitive
> -------------------------
>
> Key: MESOS-1279
> URL: https://issues.apache.org/jira/browse/MESOS-1279
> Project: Mesos
> Issue Type: Sub-task
> Components: c++ api, master, slave
> Reporter: Niklas Quarfot Nielsen
>
> As mentioned in MESOS-938, one way to support task replacement and scaling
> could be to split the responsibility into several smaller primitives for 1)
> reducing complexity 2) Make it easier to comprehend and 3) easier and
> incremental in implementation.
> resizeTask() would be the primitive to either
> 1) Scale a running task's resources down
> 2) Scale a running task's resources up by using extra auxiliary offers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
