You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Klaus Ma (JIRA)" <ji...@apache.org> on 2016/03/31 03:22:25 UTC
[jira] [Comment Edited] (MESOS-5067) Killing a framework does not
kill framework tasks
[ https://issues.apache.org/jira/browse/MESOS-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219160#comment-15219160 ]
Klaus Ma edited comment on MESOS-5067 at 3/31/16 1:21 AM:
----------------------------------------------------------
If so, how do you get task's status/result back?
was (Author: klaus1982):
If so, how do you get tasks back?
> Killing a framework does not kill framework tasks
> -------------------------------------------------
>
> Key: MESOS-5067
> URL: https://issues.apache.org/jira/browse/MESOS-5067
> Project: Mesos
> Issue Type: Wish
> Reporter: Guillermo Rodriguez
>
> By default, when a framework is terminated, mesos-master terminates all child tasks for that framework.
> There are some cases when I might like to stop a framework but not kill the tasks of the framework.
> In my particular case. I have Docker Swarm running, Swarm allows me to send number crunching jobs to the cluster and they can run for hours.
> The problem is that Swarm is also quite flaky and can crash anytime. If that happens then all jobs are terminated and all the processing time is lost.
> So, I would like to be able to set some flag for a framework where I tell mesos master that the jobs started by the framework should be considered separate of the framework itself so that the framework can be restarted and jobs will keep running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)