You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2016/01/06 21:37:39 UTC

[jira] [Commented] (AURORA-1572) SIGTERM is not sent to child processes

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

Stephan Erb commented on AURORA-1572:
-------------------------------------

I'd say that In general, it is the responsibility of a process that has allocated resources (or in this case, started child-processes) to also clean-up after itself. So I don't think the Aurora/Thermos code is at fault here, but rather the application which is not properly terminating its child processes.

Do you a specific problem that you are trying to solve?

> SIGTERM is not sent to child processes
> --------------------------------------
>
>                 Key: AURORA-1572
>                 URL: https://issues.apache.org/jira/browse/AURORA-1572
>             Project: Aurora
>          Issue Type: Story
>          Components: Executor
>            Reporter: zane silver
>            Assignee: Bill Farner
>            Priority: Trivial
>
> In terminate_process, SIGTERM is sent to the parent process only. This seems like a deliberate design choice given that the kill_process does send a SIGKILL to each child process. Is there a reason why SIGTERM is not also sent the to child processes? 
> For reference, I'm referring to the functions defined in the thermos helper.py file.



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