aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zane silver (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1572) SIGTERM is not sent to child processes
Date Wed, 06 Jan 2016 21:34:39 GMT

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

zane silver commented on AURORA-1572:
-------------------------------------

The case I'm concerned about is when cmd0 finishes, but now one of cmd1 - cmdn is running.
It won't receive the SIGTERM.

I agree that the parent process should be responsible for managing the child process. But
here it seems that commands cmd1 - cmdn are treated as children of cmd0.

> 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)

Mime
View raw message