[
https://issues.apache.org/jira/browse/MESOS-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389108#comment-14389108
]
Jie Yu commented on MESOS-2462:
-------------------------------
For example, resources accounting. Sometimes, we want to put the subprocess
into it's own cgroup. We can do that by getting the pid of the subprocess from
subprocess.pid. Now, we have two subprocesses. Technically, we should put both
subprocesses into the cgroup. However, how can I get the pid of the bookkeeping
subprocess? ALl these complication makes me think that we should just not
introduce this interface in subprocess. Also, if you look at other subprocess
impl. (e.g., in python), they don't have such interface as well.
> Add option for Subprocess to set a death signal for the forked child
> --------------------------------------------------------------------
>
> Key: MESOS-2462
> URL: https://issues.apache.org/jira/browse/MESOS-2462
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Affects Versions: 0.21.1
> Reporter: Ian Downes
> Assignee: Jie Yu
> Priority: Minor
> Labels: twitter
>
> Currently, children forked by the slave, including those through Subprocess,
> will continue running if the slave exits. For some processes, including
> helper processes like the fetcher, du, or perf, we'd like them to be
> terminated when the slave exits.
> Add support to Subprocess to optionally set a DEATHSIG for the child, e.g.,
> setting SIGTERM would mean the child would get SIGTERM when the slave
> terminates.
> This can be done (*after forking*) with PR_SET_DEATHSIG. See "man prctl". It
> is preserved through an exec call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
