Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6B74D200BB3 for ; Wed, 2 Nov 2016 21:35:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6A398160B0C; Wed, 2 Nov 2016 20:35:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B7C69160AF0 for ; Wed, 2 Nov 2016 21:34:59 +0100 (CET) Received: (qmail 66479 invoked by uid 500); 2 Nov 2016 20:34:59 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 66467 invoked by uid 99); 2 Nov 2016 20:34:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2016 20:34:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D23702C0005 for ; Wed, 2 Nov 2016 20:34:58 +0000 (UTC) Date: Wed, 2 Nov 2016 20:34:58 +0000 (UTC) From: "Zameer Manji (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AURORA-1808) Thermos executor should send SIGTERM to daemonized processes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 02 Nov 2016 20:35:00 -0000 [ https://issues.apache.org/jira/browse/AURORA-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zameer Manji updated AURORA-1808: --------------------------------- Description: 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. was: 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 back and 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. > 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)