[
https://issues.apache.org/jira/browse/MESOS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988290#comment-13988290
]
Ian Downes commented on MESOS-1279:
-----------------------------------
Containerizers should support update(Resources) which can be called at any
time, either in the scenario [~nnielsen] describes (though I believe we do add
the first task's resources into the executor's when launching?) or for
frameworks that add/remove (multiple) tasks to a running executor.
Current master cgroups code does support dynamic updating. It's brutal for
memory in that the new limit is applied, regardless of the current usage, which
could lead to immediate OOMs. We also envision that in the future some
resources, i.e., filesystem space once enforced, could be non-decreasing on
update.
> 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
> Assignee: Timothy St. Clair
>
> 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)
