You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Yifan Gu (JIRA)" <ji...@apache.org> on 2014/06/12 22:21:05 UTC

[jira] [Commented] (MESOS-1279) Add resize task primitive

    [ https://issues.apache.org/jira/browse/MESOS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029743#comment-14029743 ] 

Yifan Gu commented on MESOS-1279:
---------------------------------

Hey guys, I am interested in this too, and just put a proof of concept on the review board. Hope that will help us to push this feature.

So currently, I only plan to support resizing a single task. 

When scale up the task, the master claimed the additional resources first, and wait for the resize reply, if it succeeds, the master simply forwards the reply to the framework.
if it fails, the master recovers the resources of both the task and the allocator.

When scale down the task, the master wait for the resize reply before alternate the resources of the task and the allocator.

> 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)