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 <sumitkcha...@gmail.com> 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 <tnac...@gmail.com> wrote: > >> Are you using Docker containerizer or? >> >> Tim >> >> On Thu, Jul 20, 2017 at 10:50 PM, Chawla,Sumit <sumitkcha...@gmail.com> >> 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 <sumitkcha...@gmail.com> >> > 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 >> >> >> >> >> > >
