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 867DD200CEB for ; Sat, 29 Jul 2017 02:41:33 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 84F3616DC3A; Sat, 29 Jul 2017 00:41:33 +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 C976D16DC48 for ; Sat, 29 Jul 2017 02:41:32 +0200 (CEST) Received: (qmail 36515 invoked by uid 500); 29 Jul 2017 00:41:31 -0000 Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list dev@mesos.apache.org Received: (qmail 36465 invoked by uid 99); 29 Jul 2017 00:41:31 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Jul 2017 00:41:31 +0000 Received: from mail-ua0-f170.google.com (mail-ua0-f170.google.com [209.85.217.170]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 6964C1A05A0 for ; Sat, 29 Jul 2017 00:41:29 +0000 (UTC) Received: by mail-ua0-f170.google.com with SMTP id w45so173344626uac.5 for ; Fri, 28 Jul 2017 17:41:29 -0700 (PDT) X-Gm-Message-State: AIVw110+/SWlNDv5aboT+9XiA39rpbXbWjTXvJ0dsXQD8wEiB7tmpCvd eXnA6O3ITyKo8HsyOts15Jz2GT56quyy X-Received: by 10.159.53.36 with SMTP id o33mr6917484uao.95.1501288888783; Fri, 28 Jul 2017 17:41:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.83.13 with HTTP; Fri, 28 Jul 2017 17:41:08 -0700 (PDT) In-Reply-To: References: From: Benjamin Mahler Date: Fri, 28 Jul 2017 20:41:08 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Mesos Python Daemon Launch To: user Cc: "dev@mesos.apache.org" Content-Type: multipart/alternative; boundary="94eb2c03ce80ec449a05556a0e13" archived-at: Sat, 29 Jul 2017 00:41:33 -0000 --94eb2c03ce80ec449a05556a0e13 Content-Type: text/plain; charset="UTF-8" This is generally not something we want users to do (i.e. leak something outside of their container). Mesos will kill all tasks in the cgroup if you're using cgroup isolation, so you would have to ensure the daemon escapes the cgroup. If you're using the posix isolation, you also need to be sure the process is not "reachable" via the process tree rooted at the executor (i.e. you'll need to double fork). On Fri, Jul 21, 2017 at 1:59 AM, Chawla,Sumit wrote: > No i am not using docker container. the process is being launched > directly on host > > Regards > Sumit Chawla > > > On Thu, Jul 20, 2017 at 10:56 PM, Timothy Chen wrote: > >> Are you using Docker containerizer or? >> >> Tim >> >> On Thu, Jul 20, 2017 at 10:50 PM, Chawla,Sumit >> wrote: >> > Any clue on this one? >> > >> > The python daemon is getting launched in different session and process >> > group. Not sure why its getting killed when the mesos slave is >> terminating >> > the framework. >> > >> > Regards >> > Sumit Chawla >> > >> > >> > On Wed, Jul 19, 2017 at 4:24 PM, Chawla,Sumit >> > wrote: >> > >> >> I am using Mesos 0.27. I am launching a Python Daemon from spark task. >> >> Idea is that this Daemon should keep running even when the mesos >> framework >> >> shuts dowm. However, I am facing issues in keeping this Python Daeamon >> >> process alive. The process is getting killed as soon as Mesos >> framework is >> >> dying. >> >> >> >> >> >> >> >> Regards >> >> Sumit Chawla >> >> >> >> >> > > --94eb2c03ce80ec449a05556a0e13--