Hi Lukas, This sounds like a bug to me. Can you file a JIRA for this? We will have a look at it.
Thanks, Fang, Yan yanfang...@gmail.com On Fri, May 29, 2015 at 8:39 AM, Lukas Steiblys <lu...@doubledutch.me> wrote: > Hi Yan, > > The memory usage is not very high, but I'm trying to cut the usage any way > I can. > > The bigger problem is when the job crashes and the parent process stays > active preventing an auto restart by the Docker supervisor. > > Lukas > > On Thursday, May 28, 2015, Yan Fang <yanfang...@gmail.com> wrote: > > > Hi Lukas, > > > > The parent process is used to manage the lifecycle of the actual > process. I > > am curious how much memory the parent process takes? > > > > Thanks, > > > > Fang, Yan > > yanfang...@gmail.com <javascript:;> > > > > On Thu, May 28, 2015 at 2:30 PM, Lukas Steiblys <lu...@doubledutch.me > > <javascript:;>> > > wrote: > > > > > Hello, > > > > > > I’m running Samza tasks using ProcessJobFactory and after I start the > > job, > > > the initial process spawns a new process that is the actual process > where > > > the code is run. The problem is that the parent process stays active > even > > > after the job is started and that messes with the way I deploy Samza > (in > > > Docker containers) and consumes memory while not doing anything. > > > > > > My question: is it possible to kill the parent process while still > > leaving > > > the Samza tasks to process messages? > > > > > > Lukas > > >
