Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Fri, 16 Dec 2016 18:56:58 +0000 (UTC)
From: "Zhitao Li (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12711816.1398981837000.541850.1481914618452@Atlassian.JIRA>
In-Reply-To: <JIRA.12711816.1398981837000@Atlassian.JIRA>
References: <JIRA.12711816.1398981837000@Atlassian.JIRA> <JIRA.12711816.1398981837793@arcas>
Subject: [jira] [Commented] (MESOS-1280) Add replace task primitive
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 16 Dec 2016 18:57:00 -0000


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

Zhitao Li commented on MESOS-1280:
----------------------------------

Hi, is there any common interest in pursuing this in the next 1-2 Mesos release cycles? Our organization is quite interested in adding this capability for a couple of reasons, and would be happy if some committer is willing to shepherd us.

Thanks!

> Add replace task primitive
> --------------------------
>
>                 Key: MESOS-1280
>                 URL: https://issues.apache.org/jira/browse/MESOS-1280
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent, c++ api, master
>            Reporter: Niklas Quarfot Nielsen
>              Labels: mesosphere
>
> Also along the lines of MESOS-938, replaceTask would one of a couple of primitives needed to support various task replacement and scaling scenarios. This replaceTask() version is significantly simpler than the first proposed one; it's only responsibility is to run a new task info on a running tasks resources.
> The running task will be killed as usual, but the newly freed resources will never be announced and the new task will run on them instead.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)