apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kottapalli, Venkatesh" <VKottapa...@DIRECTV.com>
Subject RE: Reg container getting killed without throwing exceptions
Date Wed, 20 Jan 2016 23:17:37 GMT
Thanks for your inputs Gaurav and Tim.

When it is OOM, I see it in the container logs but it in this case I don’t find any.

 I see the processing part in the operator running and printing logs without any issues end
to end but not reaching the end window. It might be because of the grouping logic that we
have added  in the end window that is causing OOM but the container logs doesn’t show it.

The operator is taking long to process.  Total processed and emitted by that operator is always

I shall try to increase memory on the Application master and the container as well and see
if it works else I will try on a smaller load and see if it is a scaling issue because of

Right now, I don’t have access to the AM logs.


-----Original Message-----
From: Timothy Farkas [mailto:tim@datatorrent.com] 
Sent: Wednesday, January 20, 2016 3:11 PM
To: dev@apex.incubator.apache.org
Subject: Re: Reg container getting killed without throwing exceptions

Hey Venkatesh,

How much memory is allocated to the App Master? You should allocate atleast 2GB to app master
with this property.


Otherwise the App Master may die suddenly without printing anything to logs.


On Wed, Jan 20, 2016 at 2:47 PM, Gaurav Gupta <gaurav@datatorrent.com>

> Venkatesh,
> Did you see any OOM exception? It would be good to see the AM logs and 
> container logs to find out more.
> Thanks
> - Gaurav
> > On Jan 20, 2016, at 2:42 PM, Kottapalli, Venkatesh <
> VKottapalli@directv.com> wrote:
> >
> > Hi,
> >
> >                I get the following message when the container is 
> > getting
> killed. I don't find logs for any exceptions being thrown. How do we 
> identify the root cause for this issue?
> > Sorry for being very abstract.
> >
> > Container killed by the ApplicationMaster.
> > Container killed on request. Exit code is 143 Container exited with 
> > a non-zero exit code 143
> >
> > Regards,
> > Venkatesh.
View raw message