de 2015 11:26
Para: dev@samza.apache.org
Asunto: RE: container is running beyond virtual memory limits
I just changed the task options file to add the following line:
task.opts=-Xmx128M
And I found no change on the behaivour. I see that the job is being launched
with the default -Xmx768M value:
root
[mailto:nickpa...@gmail.com]
Enviado el: lunes, 28 de septiembre de 2015 10:56
Para: dev@samza.apache.org
Asunto: Re: container is running beyond virtual memory limits
Hi, Jordi,
Please find the config variable task.opts in this table:
http://samza.apache.org/learn/documentation/0.9/jobs/configuration
> task.commit.ms=1000
> task.window.ms=6
>
> Where do I have to change the XMX parameter?
>
> Thanks.
>
> Jordi
>
>
> -Mensaje original-
> De: Yi Pan [mailto:nickpa...@gmail.com]
> Enviado el: lunes, 28 de septiembre de 2015 10:39
> Para: dev@s
Pan [mailto:nickpa...@gmail.com]
Enviado el: lunes, 28 de septiembre de 2015 10:39
Para: dev@samza.apache.org
Asunto: Re: container is running beyond virtual memory limits
Hi, Jordi,
Can you post your task.opts settings as well? The Xms and Xmx JVM opts will
play a role here as well. The Xmx
Hi, Jordi,
Can you post your task.opts settings as well? The Xms and Xmx JVM opts will
play a role here as well. The Xmx size should be set to less than
yarn.container.memory.mb.
-Yi
On Tue, Sep 22, 2015 at 4:32 AM, Jordi Blasi Uribarri
wrote:
> I am seeing that I can not get even a single job
I am seeing that I can not get even a single job running. I have recovered the
original configuration of yarn-site.xml and capacity-scheduler.xml and that
does not work. I am thinking that maybe there is some kind of information
related to old jobs that have not been correctly cleaned when killi
