[
https://issues.apache.org/jira/browse/MESOS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188488#comment-16188488
]
Yan Xu commented on MESOS-1280:
-------------------------------
Probably not all fields in the TaskInfo make equal sense to be updatable or
justify the complexity. If possible we probably still prefer treating tasks as
cattle and want to only give them pet treatment for certain important benefits.
[~zhitao] could you elaborate on the uses cases you were thinking about? I see
that in
<https://lists.apache.org/thread.html/63233f8c92bf9ba3f4da7a8fe9066d0c33748a314546d80224ad8698@%3Cdev.mesos.apache.org%3E>
you mentioned in-place upgrades and launching zero-resource onto running
executors, among others.
I am asking because I recently started looking into something related to this.
I may poll the user/dev thread later but am starting here first.
> 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.4.14#64029)
