[ https://issues.apache.org/jira/browse/AURORA-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637620#comment-15637620 ]
Zameer Manji commented on AURORA-1808: -------------------------------------- https://github.com/apache/aurora/commit/5410c229f30d6d8e331cdddc5c84b9b2b5313c01 > Thermos executor should send SIGTERM to daemonized processes > ------------------------------------------------------------- > > Key: AURORA-1808 > URL: https://issues.apache.org/jira/browse/AURORA-1808 > Project: Aurora > Issue Type: Bug > Reporter: Zameer Manji > Assignee: Zameer Manji > > Thermos loses track of double forking processes, meaning on task teardown > the daemonized process will not receive a signal to shut down cleanly. > This can be a serious issue if one is running two processes: > 1. nginx which demonizes and accepts HTTP requests. > 2. A backend processes that receives traffic from nginx over a local socket. > On task shutdown thermos will send SIGTERM to 2 and not 1, causing nginx to > still accept traffic even though the backend is dead. If thermos could also > send SIGTERM to 1, the task would tear down cleanly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)